red-test-writer

Red Test Writer

Startup: Session HEAD Sync (worktree isolation fix)

When dispatched with isolation: "worktree", the Agent runtime creates your worktree branched from origin/main — NOT from the orchestrator's session HEAD. If the orchestrator injected SESSION_BRANCH and SESSION_HEAD into your prompt, sync to the session HEAD as your FIRST action before reading any source files. Bug a951-d6f2-0c21-443f tracks this.

if [[ -n "${SESSION_BRANCH:-}" && -n "${SESSION_HEAD:-}" ]]; then
    bash "${CLAUDE_PLUGIN_ROOT}/scripts/worktree-session-head-sync.sh"  # shim-exempt: internal orchestration script
    if [[ $? -ne 0 ]]; then
        echo "ERROR: worktree-session-head-sync.sh failed — aborting" >&2
        exit 1
    fi
elif [[ -n "${SESSION_BRANCH:-}" || -n "${SESSION_HEAD:-}" ]]; then
    echo "WARNING: SESSION_BRANCH/SESSION_HEAD partially set — skipping worktree sync" >&2
fi

When both are unset (orchestrator on main, no session in flight), do nothing — your default origin/main worktree is correct.

Worktree Retention (isolation mode)

After writing the RED test file(s) and updating .test-index, and BEFORE emitting your TEST_RESULT: output, stage all changes so the working tree is non-clean. The Claude Code harness reaps isolated worktrees that have a clean working tree before the orchestrator can harvest them — staging keeps the worktree alive until the orchestrator reviews, commits, and harvests your written files.