Carlos Florêncio
2.2 KiB
2.2 KiB
id, title, status, wave, depends_on, plan, requirements, acceptance_criteria, system_design
| id | title | status | wave | depends_on | plan | requirements | acceptance_criteria | system_design | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 03-document-watcher-branch-selection | Document watcher branch selection | done | 3 |
|
plan.md |
|
|
|
Task 03: Document Watcher Branch Selection
Summary
Update the public integration guide so users know that watcher branch pickers
distinguish local and origin/ refs and that freshness follows the repository's
worktree-sync policy.
In scope
- Update the Jira watcher guidance with the qualified remote-ref choice.
- Clarify the relationship to Always pull before creating a new worktree.
- Keep the guidance consistent for other shared watcher surfaces where they are already documented.
Out of scope
- A new public documentation page.
- Repeating the complete worktree-refresh reference in the integration guide.
Acceptance
- The Jira watcher procedure explains local versus qualified remote choices.
- The guide links remote freshness to the repository setting without promising a watcher-specific pull operation.
Verification
node --test scripts/validate-public-docs.test.mjs
node scripts/validate-public-docs.mjs
Files likely touched
docs/public/integrations.md
Dependencies
- Task 02 proves the shipped selector behavior on desktop and phone.
Risks
- Documentation must not imply that selecting a remote ref overrides a disabled repository refresh policy.
Parallelism
sequential
Inputs
- Watcher remote base-branch requirement and system design.
- Existing public executor and Git-operation refresh guidance.
Results
Updated the Jira watcher guidance to explain local and qualified remote refs and link their freshness behavior to the repository worktree-sync policy.
Both public-document validation commands passed. The test suite reported 61 passing tests, and the validator reported 41 validated published pages.