bug(Prime(post-wave) prompt): "git pull main" interpreted as switch-then-pull; orchestrator's working dir gets checked out to kahuna

[bakeb7j0]

Summary

The Prime(post-wave) prompt template in skills/nextwave/SKILL.md includes a git pull main step. Some Prime instances interpret this as "switch to main, then pull", but if the orchestrator's working dir was already on a release branch (or just shouldn't be switched), this checks out an unintended branch.

The other agent's report: skill says "stay on release branch" but Prime template's "git pull main" step is interpreted as switch-then-pull. Result: orchestrator's working dir ends up on kahuna instead of the intended branch.

Severity: low — caught by post-Prime cleanup but creates confusion in shared-checkout mode (already an anti-pattern but happens during fast iterations).

Suggested fix: rewrite the prompt to use unambiguous syntax — either git fetch origin main (no checkout) or git -C <abs-path> pull --ff-only origin main (explicit working-dir, fast-forward only).

Origin: Reported by sibling-campaign agent. @Scryer to expand and pick the rewrite.

Implementation Steps

TBD — @Scryer to expand.

Test Procedures

TBD — doc-shape regression: Prime(post-wave) template uses unambiguous fetch/pull syntax.

Acceptance Criteria

• Prime(post-wave) prompt rewritten to remove the "git pull main" ambiguity
• No instance of git pull main (without explicit -C) in any Prime prompt template

Dependencies

• None

Metadata

Severity: severity::minor
Origin: sibling-campaign tracker. @Scryer owns expansion.