Why: include the current integration baseline before verification.
Evidence: fetched origin/main=f563ed612a9574e798ee3421c010a9e2ceb416a0.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=3227dec8918dd36cbd4f8906a05ed62ffa98f3df.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Phase 6 adoption PRs merged across the formal repositories; the master record still showed PLANNED rows.
Evidence: merge commits and main CI per repository (GATE, Gitea statuses); make test-governance 421 tests OK on 2b2268f (SELF).
Impact: planning record and task card evidence only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Guidelines PR #9 review repairs ran through the shared executor; repair-r2 fail-stopped and was redone as r3.
Evidence: docs/superpowers/plans/evidence/guidelines-adoption/03-04 (SELF): governance check --guidelines-self and agent-exec validate on 7cafc7d.
Impact: planning record and evidence only.
Refs: docs/superpowers/plans/2026-10-17-guidelines-governance-adoption.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the r2 implementation unit succeeded and was integrated with scripts/agent-exec apply.
Evidence: .task/feature-governance-v2-closeout.md (SELF): governance check, agent-exec validate, adoption cases ALL PASS on 271d95f.
Impact: task card only.
Refs: .task/feature-governance-v2-closeout.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Development-Guidelines stores no process records (CONTRIBUTING.md), so its Phase 6 adoption card and evidence live with the governance master record in Dev.
Evidence: docs/superpowers/plans/evidence/guidelines-adoption/00-02 (SELF): governance check --guidelines-self, agent-exec validate, adoption cases ALL PASS.
Impact: planning records only.
Refs: docs/superpowers/plans/2026-10-16-development-governance-v2-master.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-governance-v2-closeout.md; R0=3227dec8918dd36cbd4f8906a05ed62ffa98f3df.
Impact: task metadata only; the feature workspace starts at 3227dec891.
Refs: .task/feature-governance-v2-closeout.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-auth-password-management.md; R0=a5829c271c92c2e7c525206eb831b0d6e9c877a6.
Impact: task metadata only; the feature workspace starts at a5829c271c.
Refs: .task/feature-auth-password-management.md
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-dev-shared-executor-switch.md(PR#600 into main) — 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: task-sync output must be written to the card by make evidence.
Evidence: make evidence row (SELF).
Impact: task card only.
Refs: .task/feature-dev-shared-executor-switch.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=dc01517de1cfb86abbd26dfb7932023763019d5d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the Python executor was retired through the shared executor and Phase 5/7 states changed (DM #17/#18 merged, Phase 6 pilot started).
Evidence: make test-governance 421 tests OK (SELF, card evidence); git grep finds no live Python executor reference.
Impact: task card and master record only.
Refs: .task/feature-dev-shared-executor-switch.md; DM PR #17, #18, #19
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: P5-A was rerun with the fixed shared executor (DM 42e675f) and integrated; the card must carry the run, the Python-vs-Go replay and the adoption positive/negative cases.
Evidence: make evidence rows on the card (SELF): entry tests 21 passed; replay 11 SAME, 1 expected DIFF (legacy-config, Go conforms to the contract); adoption cases ALL PASS.
Impact: task card only.
Refs: .task/feature-dev-shared-executor-switch.md; DM PR #17, #18
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-document-visualization-cockpit-i4.md(PR#598 into main) — 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: task-sync merged authoritative main (card-only change); the evidence
gate flagged prior rows as predating non-card changes, so the combo make
test was rerun at the synced head and re-recorded.
Evidence: evidence row on this card (SELF, head ddc8963).
Impact: task card only.
Refs: rollout I4
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=682a4e8263fe007cb102fc9deaf71bda514ee387.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: combo make test against frontend pin 8b59998 (Frontend #104 merged)
is green; evidence row tool-written before opening the Dev PR.
Evidence: evidence row on this card (SELF).
Impact: task card only.
Refs: rollout I4
Why: the canonical e2e.sh run (frontend c9ba344 + duty-based seed) passed
13/13 plus plain-base 2/2 — the I4 acceptance scenarios are green and the
evidence row is tool-written.
Evidence: evidence row on this card (SELF, sha256 in record).
Impact: task card only.
Refs: rollout I4
Why: The master record still showed Phases 0-4 as PLANNED after they merged.
Evidence: Dev main aee351a/682a4e8, Guidelines main 2688fd2, DM main 183e764, PR #585/#595/#596/#597.
Impact: Plan document only.
Refs: development-governance-v2
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: r1/r2 failed closed on invalid terminal records and r3 succeeded but could not be applied because both executors mis-inventory a newly added nested repository.
Evidence: receipts /tmp/p5-receipt-a-r{1,2,3}.json; apply rejection messages from scripts/agent_exec.py and dm-server 183e764.
Impact: Task card only.
Refs: development-governance-v2 Phase 5
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
