Why: Branch protection requires main in head; the synced combination
was retested and the receipt belongs to the card.
Evidence: make test exit=0 at c2e5de0d after syncing to main 42f5ac4.
Impact: Task card only.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=42f5ac4b763fcbfaf9490bb8943c970cb0f4d293.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: WP1/WP4 landed through the native/squad/backend chain; the card
records scope rulings and evidence.
Evidence: CI success on #18/#17/#71; make test exit=0 at fa0e30bd.
Impact: Task card only.
Why: Increment three landed across the chain (native #18, squad #17,
backend #71); Dev pins must point at those merged component main
heads so the tested combination is the released one.
Evidence: check-pins exit=0; native c5b9dca, squad fc9620e and
backend f0b0db9 are direct merge commits on their component mains.
Impact: Three gitlinks.
Refs: Agent-Native PR #18; Agent-Squad PR #17; Agent-System-Backend PR #71
Why: The pin cascade (#17, #69, #16, #70, #230) is part of the
delivery record; the card reflects the current merged pins.
Evidence: all five PRs merged; Dev pins at native c2befaf, squad
a75d359, backend d34c2e8; make test exit=0 at 3f824790.
Impact: Task card only.
Why: The Dev-level pin combination (native c2befaf, squad a75d359,
backend d34c2e8) passed make test; the receipt belongs to the card.
Evidence: make test exit=0 at 3f824790; check-pins exit=0.
Impact: Task card only.
Why: Squad PR #16 and Backend PR #70 completed the pin cascade;
Dev's squad and backend pins must point at those merged heads for
check-pins to verify the tested combination.
Evidence: a75d359 is the #16 merge on squad main; backend main head
is the #70 merge; backend CI passed before each merge.
Impact: Two gitlinks.
Refs: Agent-Squad PR #16; Agent-System-Backend PR #70
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=9c9483ac54ff5355c86824ac94097e65e59dcb5d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Library PR #17 and Backend PR #69 are merged; the Dev pins must
point at the merged component main heads (native c2befaf, backend
fe0c5a4) so the tested combination is the released one.
Evidence: both pins are direct merge commits on their component
mains; backend CI passed at 4075cc6 before its merge.
Impact: Two gitlinks plus the task card evidence records.
Refs: Agent-Native PR #17; Agent-System-Backend PR #69
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-rdm-phase-plan.md(already-complete) — 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 close scan only folds completed cards; the plan PRs are
approved for merge.
Evidence: Documents PR #41 and Dev PR #229 open at b8eaa16/2b1d949.
Impact: Task card only.
Why: The card and the PR description are the same document; links and
the sync record belong to the delivery record.
Evidence: Documents PR #41 and Dev PR #229 open; task-sync already up
to date at bc3f74f8.
Impact: Task card only.
Why: The evidence gate writes command output through make evidence;
commit it before the next capture so sync sees a clean tree.
Evidence: make test exit=0 at e698c646 (receipt in the card).
Impact: Task card only.
Why: Register the docs-only planning task and point the documents
gitlink at the phase-plan commit on its feature branch.
Evidence: task card carries the precheck receipt; documents commit
b8eaa16 holds the proposal.
Impact: Task card plus documents gitlink; no code changes.
Refs: docs/proposals/2026-10-07-rdm-phase-plan.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-rdm-phase-plan.md; R0=df2b72b4803a17ef1b725c3125a31529f15f3272.
Impact: task metadata only; the feature workspace starts at df2b72b480.
Refs: .task/feature-rdm-phase-plan.md
Why: Backend PR #69 and its test receipt join the delivery record.
Evidence: backend go vet + full go test ok at the backend branch head.
Impact: Task card only.
Why: preserve the independent audit of archived receipts and completed workspace disposal.
Evidence: SELF review verifies 29 receipt digests, unchanged failed-test originals and current Git cleanup state.
Impact: task records only; no code or component changes.
Refs: PR #227; .task/reviews/iterative-delivery-closure.json
Why: close the task with actual CI, merge and cleanup records and restore receipt integrity from preserved originals.
Evidence: original SELF receipt digests validate; the recorded red-green integrity check traces and repairs three metadata-substituted outputs.
Impact: archived task record only; code and component pointers are unchanged.
Refs: PR #227; .task/archive/feature-iterative-delivery.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-iterative-delivery.md(PR#227) — 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: keep the task card and PR body on the same authoritative record.
Evidence: the PR creation receipt records PR 227 and its exact source/base commits.
Impact: task metadata only; CI will verify this final PR head.
Refs: .task/feature-iterative-delivery.md; PR #227
Why: preserve the required current-base check before publishing the reviewed candidate.
Evidence: task-sync refreshed origin/main and materialized the pinned combination.
Impact: task evidence only; the resolved review fix is unchanged.
Refs: .task/feature-iterative-delivery.md
Why: archived task cards change directory and must retain an unambiguous policy reference.
Evidence: review finding 1, focused red-green proof and 104 passing governance tests are preserved in the task card.
Impact: use a repository-root text reference; record the completed review and its resolved finding.
Refs: .task/feature-iterative-delivery.md; .task/reviews/iterative-delivery.json
Why: The card tracks the WP increments; library PR #17 and its test
receipt belong in the record.
Evidence: agent-native go vet + 24-package go test ok at 9758a8d.
Impact: Task card only.
Why: present a fixed candidate with current test evidence and explicit remaining gates.
Evidence: task-sync confirmed origin/main and local full tests passed; receipts are retained in the task card.
Impact: task metadata only; implementation is unchanged from the tested candidate.
Refs: .task/feature-iterative-delivery.md
Why: preserve test and build evidence before the required clean-tree review synchronization.
Evidence: make test and make build completed on 9454819; the recorded sync refusal preserves the uncommitted-evidence check.
Impact: task evidence only.
Refs: .task/feature-iterative-delivery.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-agent-stack-n1.md; R0=2147d5cb6566c301eaea3c65448bdda873093aea.
Impact: task metadata only; the feature workspace starts at 2147d5cb65.
Refs: .task/feature-agent-stack-n1.md
Why: validate iterative delivery against the latest authoritative component combination.
Evidence: task-sync receipt in the task card records the actual merge and component materialization.
Impact: task evidence only; tests will run on this fixed candidate.
Refs: .task/feature-iterative-delivery.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=2147d5cb6566c301eaea3c65448bdda873093aea.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-agent-stack-n1q1i1-plans.md(already-complete) — 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 close scan only folds completed cards; the plans PRs are open
and the results section is filled.
Evidence: Documents PR #40 and Dev PR #226 open at e935713/46904b5.
Impact: Task card only.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-iterative-delivery.md; R0=f394bcd93bc813433203c5281c79de6865c40944.
Impact: task metadata only; the feature workspace starts at f394bcd93b.
Refs: .task/feature-iterative-delivery.md
Why: The card is the same document as the PR description; PR links
and the results section belong to the delivery record.
Evidence: Documents PR #40 and Dev PR #226 are open.
Impact: Task card only.
Why: Capture mode wrote the receipt only; import appends it to the
card so the completion declaration has its test section.
Evidence: receipt_sha256 recorded in the card evidence block.
Impact: Task card only.
Why: Register the docs-only planning task and point the documents
gitlink at the proposal commit on its feature branch.
Evidence: task card carries the precheck receipt; documents commit
e935713 holds the proposal.
Impact: Task card plus documents gitlink; no code changes.
Refs: docs/proposals/2026-10-07-agent-stack-n1q1i1-plans.md
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-agent-stack-n1q1i1-plans.md; R0=f394bcd93bc813433203c5281c79de6865c40944.
Impact: task metadata only; the feature workspace starts at f394bcd93b.
Refs: .task/feature-agent-stack-n1q1i1-plans.md
weichen