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: 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>
Why: Phase 5 Dev side needs an explicit goal, scope and acceptance before units run.
Evidence: triage NEW receipt /tmp/p5-dev-triage.json; precheck READY.
Impact: Task card only.
Refs: development-governance-v2 Phase 5
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-dev-shared-executor-switch.md; R0=aee351ae1ab8306ba4b52d74b5ba8feb9b77afda.
Impact: task metadata only; the feature workspace starts at aee351ae1a.
Refs: .task/feature-dev-shared-executor-switch.md