Why: the initiative branch's merge resolution kept a stale test_svc_recover.py that lost main's free_fixture_port helper while its callers (test_svc_superadmin_envfile) reference it, breaking the CI test job on every initiative-branch head.
Evidence: main @33d6ef69 has the helper and a fully green CI (test/test-pg/svc-realcombo success); this branch's callers now match.
Impact: Test helper alignment only; no production code.
Refs: initiative PR #635; merge af2e6b41
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=33d6ef69212595c680a744549986c19bb6acd6c3.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-rdm-two-trees-followup-c-w8-w10.md -> .task/archive/feature-rdm-two-trees-followup-c-w8-w10.md; status 已完成（合入前闭合）; PR #693https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/693.
Impact: task metadata only; the card is archived within PR #693 and lands with its merge commit.
Refs: task.sh close --self
Why: the user approved W8/W9/W10 at stage 6 on 2026-10-22; RDM #470 and FE #125 merged after CI; the knowledge-multi-mount DTO and RDM review MINORs move to increment D, W11/W12 stay pending resource authorization.
Evidence: CI success at RDM 4951086 and FE a82a1e1 (both after merging latest main).
Impact: Task card only.
Refs: stage-6 review reports on this branch (docs/reviews/2026-10-22-increment-c-*)
Why: agent-per-unit governance requires review and repair attempts recorded in the increment C card.
Evidence: reviews 0 BLOCKING (RDM 5 MAJOR, FE 3 MAJOR) repaired in d835ae6 / 4882e0a; SELF domain/rdmapp/plugins and design-guard/workspace tests all ok.
Impact: Task card only.
Refs: parent initiative feature/rdm-two-trees-followup
Why: agent-per-unit governance requires the attempt recorded in the increment C card.
Evidence: w10-audit-workspace completed via cursor (attempt 2 after a legitimate scope-expansion re-dispatch); transport fa08be4 on FE branch feature/rdm-two-trees-followup-w10; SELF design-guard 7/7, component tests 33/33, build ok.
Impact: Task card only.
Refs: stage-5 plan W10; parent initiative feature/rdm-two-trees-followup
Why: agent-per-unit governance requires the attempt recorded in the increment C card.
Evidence: w9-rdm-audit-adapter completed via cursor attempt 1; transport c4c6df7; pin advanced to backend main 92a41183 (X1+X2+MINORs); SELF build/vet ok and domain/rdmapp/plugins tests all ok.
Impact: Task card only.
Refs: stage-5 plan W9; backend PR #243
Why: agent-per-unit governance requires each implementation attempt recorded in the task card.
Evidence: w8a 6fd0478 and w8b c3d3111 (attempt 2 after an infra retry); SELF vet ok and domain/rdmapp/plugins tests all ok.
Impact: Task card only.
Refs: stage-5 plan W8; parent initiative feature/rdm-two-trees-followup
Why: agent-per-unit governance requires each implementation attempt recorded in the increment C card.
Evidence: w8a-operation-audit-core completed via cursor attempt 1; transport 6fd0478; SELF gofmt/vet ok, domain+rdmapp tests ok.
Impact: Task card only.
Refs: stage-5 plan W8; parent initiative feature/rdm-two-trees-followup
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-rdm-two-trees-followup-c-w8-w10.md; R0=f23f5bb01a8b96ab90686d3a1b07791d7f473de2.
Impact: task metadata only; the feature workspace starts at dcca511292.
Refs: .task/feature-rdm-two-trees-followup-c-w8-w10.md
Why: increment B (W5/W6/W7a) passed user stage-6 and merged across the three repos; the charter requires the subtask registry and current stage to reflect it.
Evidence: RDM #458 merged 93badd7e; Dev #666 merged c76e681; backend #231 merged 7a41f22e; stage-6 package on the child branch.
Impact: Task card only.
Refs: child card feature-rdm-two-trees-followup-w5-w7 (PR #666)
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-rdm-two-trees-followup-w5-w7.md -> .task/archive/feature-rdm-two-trees-followup-w5-w7.md; status 已完成（合入前闭合）; PR #666https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/666.
Impact: task metadata only; the card is archived within PR #666 and lands with its merge commit.
Refs: task.sh close --self
Why: the user approved W5/W6/W7a at stage 6 on 2026-10-20; X1 tag stays unpublished (W7 provider wiring remains gated) and the RDM review MINORs move to increment C per the package proposal.
Evidence: RDM PR #458 merged 93badd7e after CI success; backend PR #231 merged 7a41f22e after CI success.
Impact: Task card only.
Refs: stage-6 package docs/superpowers/specs/2026-10-20-rdm-two-trees-followup-w5-w7-review.md
Why: W5/W6/W7a are independently reviewed (RDM 0 blocking after repair, backend 7/7 pass) and the increment has reached the user stage-6 gate; the package consolidates evidence, transports and known limits.
Evidence: review reports committed on the RDM and backend branches; repair unit transport 04991ed; backend PR #231 CI green at 8c410b9.
Impact: Task card and review package docs only.
Refs: parent initiative feature/rdm-two-trees-followup (PR #635)
Why: the user approved the source-recheck r1 revision; the isolated W6 branch was merged with current main and the completion unit audited and closed the remaining revision gaps.
Evidence: w6-x1-recheck-completion completed via cursor attempt 1; transport 8c410b9 on backend feature/w6-x1-source-recheck; SELF build/vet and store/runmgr/workflow/extension tests all ok.
Impact: Task card only.
Refs: rdm-two-trees-stage6-w6-source-recheck-design-adjustment-r1.md; backend candidate 6ba53e4
Why: W7a (pure domain bundle builder) is delivered within the plan's no-tag constraint; W6 stays paused pending the pending-review design revision the stage-6 doc requires the user to approve.
Evidence: w7a-project-context-domain completed via cursor attempt 1; transport 8327603; SELF vet ok, rdmapp tests ok, zero pkg/extension imports.
Impact: Task card only.
Refs: rdm-two-trees-stage6-w6-source-recheck-design-adjustment-r1.md
Why: record the second W5 implementation attempt per agent-per-unit governance.
Evidence: w5b-trace-impact-endpoints completed via cursor attempt 1; transport 2e5fcb7 on the RDM child branch; SELF vet ok and rdmapp+plugins/rdm tests all ok.
Impact: Task card only.
Refs: RDM branch feature/rdm-two-trees-followup-w5-w7
Why: agent-per-unit governance requires each implementation attempt to be recorded with its transport and receipt.
Evidence: w5a-tracenet-domain-core completed via cursor attempt 1; transport a7a6df0 on the RDM child branch; SELF gofmt/vet and domain+rdmapp tests all ok.
Impact: Task card only.
Refs: RDM branch feature/rdm-two-trees-followup-w5-w7
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-rdm-two-trees-followup-w5-w7.md; R0=ed3847c85ce111a74f0cb100908abfb40f62db07.
Impact: task metadata only; the feature workspace starts at 13b9c9dadd.
Refs: .task/feature-rdm-two-trees-followup-w5-w7.md
Why: The user authorized starting increment B (W5-W7) of the two-trees follow-up initiative; the charter requires each increment to be registered as a child task with scope, authorization and stage-6 endpoint before implementation.
Evidence: Card records R0 82b581d (parent initiative HEAD, synced and green), RDM base ed3a0f9, sequence W5-W6-W7, and the no-merge stage-6 endpoint.
Impact: Task card only; no source changes.
Refs: parent card .task/feature-rdm-two-trees-followup.md
Why: The local initiative branch merged main without its own remote advance (8 commits: W3-rest delivery, stage-6 approval, PR #641 merge); combining both keeps the branch history complete.
Evidence: git rev-list HEAD..origin/feature/rdm-two-trees-followup drops to 0 after this merge; card shows W3-rest approved and folded.
Impact: Branch bookkeeping only; no source changes.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=7e6c544b3c25c510e3d928bfb4515937a1cd6696.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-rdm-two-trees-followup-w3-rest.md -> .task/archive/feature-rdm-two-trees-followup-w3-rest.md; status 已完成（合入前闭合）; PR #641https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/641.
Impact: task metadata only; the card is archived within PR #641 and lands with its merge commit.
Refs: task.sh close --self
Why: The user approved the W3 remainder at stage 6 on 2026-10-20 and authorized merging RDM #451 into RDM main.
Evidence: RDM #451 merged at 76b4c05 after head f3fa0c0 status success; merged tree 4cfacf16 matches the pre-merge merge-tree.
Impact: Task cards and review package only; W4 write entry points must first add node placement checks.
Refs: Agent-System-RDM#451, Agent-System-Dev#641
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the task card and PR description are one document and must point at each other.
Evidence: PR #641 opened against feature/rdm-two-trees-followup.
Impact: task card only.
Refs: PR #641
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: W3 remainder is implemented on RDM draft PR #451 and needs the user's stage 6 review before merging into the initiative.
Evidence: RDM f3fa0c0 target tests and domain/rdmapp packages pass locally (SELF); fresh-session review PASS-with-fixes with no blocking findings.
Impact: task cards and review docs only; placement checks recorded as a W4 write-entry prerequisite.
Refs: feature/rdm-two-trees-followup-w3-rest, RDM PR #451
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: record the authorized end point and scope for the W3 remainder child task.
Evidence: card fields only (SELF).
Impact: task card only.
Refs: docs/superpowers/specs/2026-10-19-rdm-two-trees-followup-a1-review.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-rdm-two-trees-followup-w3-rest.md; R0=2b7fdc39a1f44163f4766701429d61ffd6926f1a.
Impact: task metadata only; the feature workspace starts at 9e6d9690f6.
Refs: .task/feature-rdm-two-trees-followup-w3-rest.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=2b7fdc39a1f44163f4766701429d61ffd6926f1a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The two-trees follow-up initiative needs its first increment (W0 catalog
guard, dynamic svc test ports, W3 gap check) packaged for user stage 6 review.
Evidence: Targeted unittest run on 000a2d2 recorded in the task card (SELF);
PR CI on the final HEAD is the GATE.
Impact: Task card and review spec only; implementation landed via agent-exec
transport 000a2d2.
Refs: .task/feature-rdm-two-trees-followup.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-rdm-two-trees-followup.md; R0=46e331a7a81c94c6f5881c997ae0aca45664c830.
Impact: task metadata only; the feature workspace starts at 46e331a7a8.
Refs: .task/feature-rdm-two-trees-followup.md
weichen
