Why: Gitea containers may leave SIGKILLed children as zombies until PID 1 reaps them, while kill -0 still reports success.
Evidence: Both timeout tests and the full AgentExecControllerTests suite pass; git diff --check passes.
Impact: Changes test liveness detection only; genuinely running child processes still fail the assertions.
Refs: #567
Why: PR #567 CI runs without a global Git user identity, causing every successful agent transport commit to fail with exit 128.
Evidence: The focused no-identity regression plus AgentExecControllerTests and AgentExecHistoryTests pass (30 executions total); git diff --check passes.
Impact: Supplies a deterministic non-secret identity only to git commit-tree; routing, receipts, and transport validation are unchanged.
Refs: #567
Why: Record the fixed-candidate validation and independent fresh-session review before opening the delivery PR.
Evidence: PI MiniMax-M3 session 01a13eb4-5e25-70e9-95ae-2342ec525fac reported NO_FINDINGS for fec42e0320c458a8aa060ce9295f332a3ec6d58d; make test and make build passed.
Impact: Updates only delivery metadata; implementation behavior is unchanged.
Refs: feature/goal-first-delivery
Why: execution history intentionally adds one source-external Git metadata path after every run
Evidence: focused fallback and history tests
Impact: preserves the no-canonical-implementation assertion while accepting the history record
Refs: feature/goal-first-delivery
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=919f75cf7b39ca357e212a08a0ba5ba3d9a79b51.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: align the task card with the completed three-CLI routing and execution-history scope
Evidence: source-external probe receipts and git diff --check
Impact: marks implementation complete and final delivery gates pending
Refs: #518
Why: retain which CLI handled each task so routing can improve from real outcomes over time
Evidence: AgentExecHistoryTests and git diff --check
Impact: appends sanitized source-external JSONL records without changing run outcomes
Refs: feature/goal-first-delivery
Why: make the three approved CLIs the only active implementation and test routes
Evidence: adapter unit tests, configuration validation, diff check, and real marker probes for all three profiles
Impact: narrows project routing and fixes agy prompt binding for noninteractive execution
Refs: feature/goal-first-delivery
Why: verify configured Agent CLIs one profile at a time before declaring them usable
Evidence: 53 focused tests, agent-exec validation, 397-test governance regression, and diff check
Impact: adds opt-in source-external probes, acceptance checks, and current task records
Refs: U5; docs/superpowers/plans/2026-10-15-project-agent-execution.md
Why: Hide provider-specific noninteractive, model, permission, workspace, prompt, and output differences behind one adapter seam.
Evidence: Cursor observed red then 22 green config/adapter tests; the host replays them and whitespace checks during integration.
Impact: Adds deterministic direct-argv adapters and probes without launching providers or enabling project routing.
Refs: docs/superpowers/plans/2026-10-15-project-agent-execution.md
Why: Establish one validated project-local routing document before any real Agent execution is enabled.
Evidence: Cursor observed red then 12 green configuration tests; the host replays those tests, the temporary validation target, and whitespace checks during integration.
Impact: Adds the U1 configuration contract and parser only; real routing, adapters, controller execution, and governance adoption remain disabled.
Refs: docs/superpowers/plans/2026-10-15-project-agent-execution.md
Why: Turn the approved multi-CLI routing design into independently testable Cursor implementation units without another manual plan gate.
Evidence: The plan self-review found R1-R10 coverage, stable interfaces, five review-focus tests, and no placeholders or whitespace errors.
Impact: Authorizes U1-U5 execution through fresh Cursor Agent runs while the host retains scope, verification, integration, and delivery control.
Refs: docs/superpowers/specs/2026-10-15-project-agent-execution-design.md
Why: Let each project route expensive implementation work across available Agent CLIs while the host model retains planning and delivery control.
Evidence: The specification passed placeholder, consistency, scope, path, and whitespace self-checks; implementation and runtime validation remain NOT_RUN.
Impact: Defines a review-only R1-R10 design for Markdown configuration, adapters, run-everything execution, receipts, recovery, and host fallback without enabling the new route.
Refs: .task/feature-goal-first-delivery.md
Why: Preserve the stage-six approval, resolved synchronization result, and exclusive final-window claim before fixing the tested candidate.
Evidence: make task-sync incorporated origin/main at cc40e10 with changed=0 after the conflict-resolution merge; queue claim is issue #518 comment 6478.
Impact: Advances this task to formal verification without changing implementation behavior or expanding its scope.
Refs: .task/feature-goal-first-delivery.md
Why: Synchronize the approved policy candidate with the active simplified merge-window rules now on origin/main.
Evidence: Resolved the two semantic conflicts by preserving upstream queue simplification and this task's goal-first/cursor-per-unit contract; focused task-card regression and cached diff checks passed.
Impact: Retains the active single-window delivery process while replacing mechanical stage approvals with necessary decisions and preserving Cursor-per-unit execution.
Refs: .task/feature-goal-first-delivery.md
Why: Keep the task authority, execution attempts, and stage-six candidate state recoverable.
Evidence: make evidence captured the controller status for P2 at canonical commit d79d6c17 and the run-wide governance verification receipt.
Impact: Records one failed no-change attempt, one successful Cursor attempt, host integration, and all remaining NOT_RUN stages without changing implementation behavior.
Refs: .task/feature-goal-first-delivery.md
Why: Ensure implementation authorship is delegated per unit while the primary model remains responsible for planning and delivery management.
Evidence: The focused task-card generation regression went red then green, and git diff --check passed.
Impact: Every repository-writing implementation unit gets a fresh Cursor CLI run; unavailable or failed Cursor work is recorded as a blocker instead of being silently implemented by the primary model.
Refs: .task/feature-goal-first-delivery.md
Why: Keep authorized work focused on its stated outcome, prevent private scope expansion, and remove mechanical human stage gates.
Evidence: make test-governance passed 344 tests with 18 environment-dependent skips; receipt is recorded in the task card.
Impact: New tasks use goal-first execution while retaining real decision points, independent review, evidence, platform admission, and high-consequence dual keys.
Refs: .task/feature-goal-first-delivery.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-goal-first-delivery.md; R0=33261925a10c4eee40d1b6175b3895e78a47ef02.
Impact: task metadata only; the feature workspace starts at 33261925a1.
Refs: .task/feature-goal-first-delivery.md
weichen