Why: The archived child cards still showed NOT_RUN for review, merge and cleanup although all three happened.
Evidence: PR #595/#596 review comments (REPLAY) and CI (GATE); task-finish exit 0 for both child worktrees.
Impact: Archived task cards only.
Refs: PR #585, PR #595, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: branches merged into their immediate or root target had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-development-governance-v2-triage-hardening.md(PR#595 into feature/development-governance-v2) — merges verified via git log --merges plus Gitea API squash lookup against each card's origin target.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: branches merged into their immediate or root target had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-development-governance-v2-target-integrity.md(PR#596 into feature/development-governance-v2) — merges verified via git log --merges plus Gitea API squash lookup against each card's origin target.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: Phase 4 requires task-sync and the final initiative PR check before review and merge.
Evidence: make evidence SELF receipts for make task-sync (changed=0, sync_base aa3c7ea) and make task-pr-check PR=585 FINAL=1 (PR_CHECK_OK kind=initiative).
Impact: Task card only.
Refs: PR #585
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Phase 3 requires evidence that real children flowed child -> initiative and that a frozen initiative rejects new children.
Evidence: make evidence SELF receipt for task-triage (NEW) and forced JOIN refusal (exit 7); PR #595/#596 Review and CI records.
Impact: Task card only.
Refs: PR #585, PR #595, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Both required children (#595, #596) are merged; the initiative must stop accepting new requirements before final delivery.
Evidence: PR #596 merged as 41bf47c with test/test-pg/svc-realcombo green on 00ae760.
Impact: Task card only; triage no longer offers this initiative as a JOIN candidate.
Refs: PR #585, PR #596
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.4 completed with the documented local-clone gitlink pattern; the child is ready for review.
Evidence: make evidence test-governance (1 environmental port conflict) and check-pins (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current parent initiative baseline before verification.
Evidence: resolved feature/development-governance-v2=208f4e8db73cb7f99f62b173000898da3136a0d2.
Impact: integrate parent initiative changes without rewriting task history.
Refs: task-sync
Why: The worker initialised the submodule, which changed git administration state in its private clone.
Evidence: /tmp/gov2-receipt-u24-r1.json terminal failed-unknown, no transport (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Phase 5-7 depend on how repositories obtain the shared executor and how CI reads private submodules.
Evidence: Owner answers on 2026-10-17; DM secret list shows SUBMODULE_TOKEN (SELF).
Impact: Governance master plan only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.2 completed on a fresh run after a scope-expansion stop and was applied by transport.
Evidence: make evidence run of task/recovery/evidence/triage/pr-check tests (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-target-integrity.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-development-governance-v2-target-integrity.md; R0=aa3c7eae40264ee47d5505a162074cfd77b1a099.
Impact: task metadata only; the feature workspace starts at 3524ffd3cc.
Refs: .task/feature-development-governance-v2-target-integrity.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=aa3c7eae40264ee47d5505a162074cfd77b1a099.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Phase 2 needs a second child created through the new triage flow, and --final needs a child registry.
Evidence: PR #595 merged into the initiative as ba029e4 (GATE run 3488).
Impact: Initiative task card only; intake is closed again after the second child merges.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.3 completed and was applied by transport; the first run was rejected before start.
Evidence: make evidence run of test_task_pr_check and test_ci_credentials (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-triage-hardening.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U2.1 completed on the sixth fresh run and was applied by transport.
Evidence: make evidence run of task.sh syntax and 119 triage/task tests (SELF).
Impact: Task card only.
Refs: .task/feature-development-governance-v2-triage-hardening.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Both runs ended failed-unknown and must be reconciled before a fresh dispatch.
Evidence: /tmp/gov2-receipt-u21-r5.json, /tmp/ops-receipt-disable-cursor-dev.json (SELF).
Impact: Task card only; nothing integrated.
Refs: .task/feature-development-governance-v2-triage-hardening.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the worker exited before reaching the model because of a TLS network failure.
Evidence: /tmp/gov2-receipt-u21-r4.json; private workspace clean, no remote.
Impact: task metadata only.
Refs: PR #585
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the worker's terminal record was followed by a code fence and failed closed.
Evidence: /tmp/gov2-receipt-u21-r3.json; private clone had no remote and no commits.
Impact: task metadata only.
Refs: PR #585
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: two U2.1 runs ended failed-unknown and were reconciled before a fresh run.
Evidence: receipts /tmp/gov2-receipt-u21.json and -r2.json; private clones had no remote and no commits.
Impact: task metadata only.
Refs: PR #585
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-development-governance-v2-triage-hardening.md; R0=82c8989973112d0533ee7c70654c907269df7859.
Impact: task metadata only; the feature workspace starts at d46dec31de.
Refs: .task/feature-development-governance-v2-triage-hardening.md
Why: the task card claimed all units complete while confirmed blocking defects remain in triage and the Guidelines contract.
Evidence: review of task.sh triage (count-based JOIN, local-only scan) and Guidelines PR #7 diff; CI runs 3417/3419 apply only to superseded objects.
Impact: initiative stops accepting requirements; status uses the PLANNED..CLOSED model; remaining phases tracked in one master record.
Refs: PR #585, Guidelines PR #7
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=82c8989973112d0533ee7c70654c907269df7859.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why:
- Record verified Gitea CI status (run 3417: test, test-pg, svc-realcombo all passed).
- Update current stage to testing completed (ready for review and merge).
Evidence:
- Gitea CI run 3417 jobs 5353, 5354, 5355 all succeeded.
Impact:
- Keeps task card synchronized with authoritative GATE verification evidence.
Refs:
- PR #585
Why:
Provide phased rollout roadmap (Phases 1-5) for stock repositories and mandatory defaults for new projects under governance v2.
Evidence:
Specification documented in docs/superpowers/specs/2026-10-16-stock-repos-adoption-matrix.md.
Impact:
Clarifies U6 and U7 governance deliverables for multi-repo rollout without ambiguity.
Refs:
feature/development-governance-v2
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=84900d44d34d2d42428a5b5de1d92328d90a9950.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why:
Declare feature/development-governance-v2 as an initiative branch accepting requirements and record U4 agent execution receipt.
Evidence:
Tested task-triage detecting active initiative branch; U4 receipt recorded in /tmp/receipt-u4.json.
Impact:
Task card metadata updated; no code changes.
Refs:
feature/development-governance-v2
Why:
Audit differences between Agent-System-Dev agent_exec.py and Development-Manager runner.go to clarify layer responsibilities for governance v2.
Evidence:
Architecture specification document created in docs/superpowers/specs/.
Impact:
Provides guidance for U3 shared executor convergence without duplicating logic across repositories.
Refs:
feature/development-governance-v2
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-development-governance-v2.md; R0=e665bfb574fe3311bb1ffa02212c0620c4e310f7.
Impact: task metadata only; the feature workspace starts at e665bfb574.
Refs: .task/feature-development-governance-v2.md
weichenandCursor