Why: Preserve final root/child offline resume behavior and its reachable-parent-missing guard.
Evidence: 80 evidence/recovery tests and all 491 governance tests pass (18 expected skips) on the code candidate.
Impact: Local resume remains bounded; known missing remote parent refuses, network outage may use the registered local parent. Final-head CI remains required.
Refs: U2 / PR #618
Why: Preserve host verification and worker transport records for offline root and child task resume.
Evidence: 79 evidence/recovery tests passed; governance validation is being rerun on the final implementation candidate.
Impact: LOCAL_READY remains local-only; exact-head CI and final independent review remain required.
Refs: U2 / PR #618
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-iam-u4-role-authority.md -> .task/archive/feature-iam-u4-role-authority.md; status 已完成（合入前闭合）; PR #619https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/619.
Impact: task metadata only; the card is archived within PR #619 and lands with its merge commit.
Refs: task.sh close --self
Why: Backend v0.6.0/v0.7.0 were published, RDM #440 and #441 merged, and Dev now pins the merged component mains.
Evidence: GATE CI success on RDM 7795952 and 607af47; transports 607af47 and a71c68c (SELF receipts under /tmp/cleanup-20261018/render).
Impact: card only.
Refs: RDM PR #440, RDM PR #441
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: three U4 component PRs passed CI and merged under merge_then_accept.
Evidence: GATE CI success on PR heads b4a19e7, 4d7dffe, 0b16daf and on Backend main 6594e1d; merged main trees equal the PR heads.
Impact: card only; RDM and Dev remain pending the Backend v0.6.0 and v0.7.0 tags.
Refs: Backend PR #213, Frontend PR #111, Documents PR #114
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Documents merged main cleanly and Dev was re-based onto main with the synced component pins, so the stage 7 manifest must name the new heads.
Evidence: make task-sync evidence block (SELF) synced to main 11e40e7 at tested head 72ccd31.
Impact: card only.
Refs: Dev card feature-iam-u4-role-authority
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev main moved 479 commits ahead and the U4 component branches were
re-synced onto their mains after the renderer line; the old gitlinks
conflicted with main's renderer pins. The user authorized syncing U4 after
the renderer line on 2026-10-18.
Evidence: content is the agent-exec transport ce403ff (cursor worker, unit
dev-iam-u4-onto-main-11e40e7-r1, receipt
/tmp/cleanup-20261018/render/u4-dev-onto-run.json, SELF), integrated with
agent-exec apply onto main 11e40e7; this merge (strategy ours) only records
U4 commit b081484 as an ancestor and changes no content. Non-gitlink paths
equal the mechanical merge tree d944fe8.
Impact: modules/backend -> b4a19e7, modules/frontend -> ac45aa7,
modules/documents -> 0b16daf; architecture baseline gains the backend/authz
edges; the U4 card carries the replayed stage 7 evidence.
Refs: Dev card feature-iam-u4-role-authority
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the renderer line merged into Backend, Frontend and RDM main, so the
2026-10-15 stage 7 candidates were superseded under DR21 and the evidence
had to be replayed before acceptance.
Evidence: card evidence blocks (SELF) for the live acceptance harness 18/18
on Backend b4a19e7, RDM bdf65fe, Frontend ac45aa7 and UI 5c2b103; RDM go vet
and go test on the U4 Backend overlay; Backend go vet and go test; Frontend
vitest and build. One RDM run with a stale overlay path failed and stays
recorded.
Impact: the candidate manifest and the DR mapping header now name the new
heads; Documents and Dev sync remain pending.
Refs: Backend PR #209, Frontend PR #106, RDM PR #440
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Preserve the final guard for a reachable advertised target whose commit object cannot be compared locally.
Evidence: The regression test, 74 focused evidence/recovery tests, and all 485 governance tests pass.
Impact: Network outages retain LOCAL_READY; known but unverified target history returns REMOTE_UNVERIFIED. Exact-head CI remains pending.
Refs: U2 / PR #618
Why: Preserve the final test matrix and review corrections for the U2 candidate.
Evidence: All 484 governance tests pass (18 skipped); the targeted evidence and recovery cases pass on the same implementation.
Impact: SELF evidence only; final-head CI and independent review remain required.
Refs: U2 / PR #618
Why: Deliver the regulations knowledge base plan U1-U9 and pin the composition in Dev.
Evidence: CI success on f5b5568 (test, test-pg, svc-realcombo); component main CI recorded on the archived task card.
Impact: Specs, four gitlinks (backend 56a7f9f, documents 5bb4877, frontend 50ec836, ui 5c2b103) and the opt-in make test-regulations-kb gate.
Refs: https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/614
Why: Preserve the closed-task and remote-target rewind corrections with their regression and governance test evidence.
Evidence: 71 focused tests and all 482 governance tests passed; the previous exact-head CI failed in an unrelated backend runtime test and requires a fresh run.
Impact: Review findings are fixed in scope; independent final review and current-head CI remain required.
Refs: U2 / PR #618
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-regulations-kb.md -> .task/archive/feature-regulations-kb.md; status 已完成（合入前闭合）; PR #614https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/614.
Impact: task metadata only; the card is archived within PR #614 and lands with its merge commit.
Refs: task.sh close --self
Why: Earlier receipts predate the main merge and frontend re-pin; key checks were rerun on the current head.
Evidence: make test exit 0 and make test-regulations-kb exit 0 at 0f6310a via make evidence.
Impact: Task card only.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U8
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Final window requires a fresh task-sync record.
Evidence: make task-sync via make evidence (sync_base a5f3ce5).
Impact: Task card only.
Refs: policy/delivery.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: All plan units U1-U9 are merged in their component repositories; the card must reflect delivery, verification and remaining NOT_RUN items before the final window.
Evidence: Component main CI statuses (GATE) and local make test / make test-regulations-kb receipts (SELF) on the card.
Impact: Task card only; initiative stops accepting requirements.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The U8 Dev composition needs SELF evidence for the full Dev suite and the regulations gate.
Evidence: make evidence rows for make test (two honest failures from uninitialized nested submodules and umask 077, then exit 0) and the regulations gate (exit 0).
Impact: Task card only.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U8
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Capture the final offline recovery cases and host verification on the PR candidate.
Evidence: 68 focused evidence and task-recovery tests pass; two broader task-start failures reproduce on the parent baseline.
Impact: Local evidence remains SELF; exact-head CI and independent review are still required.
Refs: U2 / PR #618
agent-exec-transport
weichen