Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-finish-guard-fixes.md; R0=4edec763fff1b8239e203dc9106f16a241ca343d.
Impact: task metadata only; the feature workspace starts at 4edec763ff.
Refs: .task/feature-finish-guard-fixes.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-governance-reliability.md(PR#213) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: the owner authorized conflict-free integration and safe worktree cleanup after verification.
Evidence: final fixed combination passes make test and make build; full outputs and review replay records are in the task card.
Impact: authorization and evidence metadata only; no source or component change.
Refs: .task/feature-governance-reliability.md
Why: bind the reviewable governance repair to the synchronized candidate and related component PRs.
Evidence: tool-generated SELF make test and make build output plus independent repair REPLAY records in the task card.
Impact: task metadata only; platform protection and deployment remain owner-controlled.
Refs: .task/feature-governance-reliability.md
Why: main advanced with merged-task-name and legacy evidence guards during this task.
Evidence: SELF 44 lifecycle regressions pass after resolving both hunks; independent review repairs are recorded in the task card.
Impact: retains both task-start protections and the stronger JSON/legacy receipt reader, without rewriting either branch history.
Refs: Dev PR #211 and #212; .task/feature-governance-reliability.md
Why: independent review found shared submodule metadata risk, quoted header leakage, stale JSON receipt blindness and missing abandon coverage.
Evidence: SELF 92 governance regressions pass; the original review receipt and replay output are recorded in the task card.
Impact: preserves external component worktrees, handles both evidence formats and adds targeted failure-path coverage; no product behavior changes.
Refs: .task/feature-governance-reliability.md; .task/reviews/governance-reliability.json
Why: retain complete tool-generated local verification for the governance repair candidate.
Evidence: SELF task-sync, 75 governance tests, full make test, make build and syntax checks are recorded in the task card.
Impact: evidence metadata only; product and gate implementations are unchanged.
Refs: .task/feature-governance-reliability.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-task-start-merged-guard.md(PR#211) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: cleanup, component synchronization, receipt recording and credential handling could contradict the documented development boundaries.
Evidence: SELF 75 isolated governance tests and source checks are captured in .task/feature-governance-reliability.md; combination and CI verification follow.
Impact: hardens local task and CI tooling, aligns policy and component documentation, and adds continuous regression tests without changing product behavior.
Refs: .task/feature-governance-reliability.md; policy/governance.md; policy/platform-admission.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-ext-1-inproc-handler.md(PR#209) — merges verified via git log --merges against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
Why: the completion claim needs a make test evidence row whose tested HEAD is this branch, not the discarded template commit.
Evidence: make evidence captured make test exit 0.
Impact: task card only.
Refs: PR #207
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the recreated branch needs its own evidence rows for the checks that already passed on the merged implementation.
Evidence: precheck, cmdbus/rag/app/extension tests, downstream example, and boundary lint, written by make evidence.
Impact: task card only.
Refs: PR #207
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: task-start recreated feature/ext-1-inproc-handler on main and replaced the card already merged in PR #207 with an empty template.
Evidence: restored content matches 63a62a79ac; no product code change.
Impact: this branch tip keeps the merged card instead of deleting it.
Refs: PR #207
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
