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: 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: 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: 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