Worktree integration

Inputs

For each candidate, require:

• task ID;
• base SHA;
• reviewed head SHA;
• complete reviewed base-to-head range or ordered commit list, with prerequisites;
• task attempt/state and relevant contract/dependency revision;
• validation summary;
• known risks and omissions.

Procedure

1. Create a dedicated integration branch/worktree from the intended base. Reuse one only after inspecting its state and preserving retained work.
2. Integrate exact reviewed SHAs in dependency order.
3. Resolve only mechanical conflicts where intent is unambiguous.
4. Return semantic conflicts or changed assumptions to the owning implementation agent/Lead.
5. Build the assembled application and run repository-required integration checks.
6. If user-visible behavior changed, run the integrated UI-validation gate.
7. Record the final integration SHA and evidence.
8. Push/open a PR only when repository policy permits.

Never substitute an unreviewed moving branch tip for a reviewed SHA.

Require affirmative completed review evidence for that candidate. Neutral, skipped, budget-exhausted, interrupted, or stale checks do not satisfy this gate, even if the hosting provider accepts their status. Return incomplete gates to the coordinator without starting a review loop yourself.

Confirm what the review covers before choosing an integration operation. A named head commit is not automatically the whole change set for cherry-picking. Record the source-to-integrated mapping and verify that the assembled tree includes the complete approved change. Keep approval bound to the candidate and attempt it actually reviewed.

If a writer hands off a patch because Git writes were denied, an authorized coordinator must record and validate its commit before it enters this reviewed-candidate workflow. For QA evidence, distinguish product SHA, authored test SHA, and combined revision exercised. Record relevant dirty state with command results; a clean-looking HEAD alone cannot identify uncommitted tested code.

Integrate assigned documentation changes before final checks. Run affected docs/example checks and inspect relevant generated pages. New edits or conflict resolutions that alter reviewed content require a new candidate revision and refreshed affected review and validation. Ordinary assembly still requires integration evidence for the combined result.

Use package-readiness for assigned package candidates and technical-writing with unslop for PR, release, and migration prose. Retain failing QA reproducers until the defect is resolved; do not remove evidence solely to make the branch green.