Why: Operators need the approved no-password initialization and owner-confirmed recovery contract, and stage 6 reviewers need an exact component/evidence map.
Evidence: SELF task-card precheck and make test-governance receipts; component receipts listed in the task card with separate source identities.
Impact: svc rejects obsolete credential commands before storage binding, help points to protected delivery and recovery proposals, and the task card records stage 6 scope with formal pin/CI dependencies still pending.
Refs: IAM U3 r1 Documents c236d309; Backend 3e01614; RDM 265d33e; Frontend a961b19
Why: bind the human review checkpoint to the authoritative baseline and fixed contract.
Evidence: SELF task-sync and document-check receipts captured by make evidence.
Impact: evidence metadata only; business tests, CI and runtime delivery remain NOT_RUN.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM U3 phase 4-5
Why: preserve the authorized U3 scope and concrete contract for human phase review.
Evidence: SELF startup and document-check receipts; independent document review of fixed drafts.
Impact: task metadata only; no product code, runtime data, production operations or gitlink changes.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM r1 U3
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-iam-u3-account-directory-recovery.md; R0=add097d06137c4912a4ed9279e98ca353e4e4cf1.
Impact: task metadata only; the feature workspace starts at add097d061.
Refs: .task/feature-iam-u3-account-directory-recovery.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=57bcb17ea212a531186b6e21617a7f3bea65a791.
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-merge-queue-policy-draft.md(PR#519) — 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 user requires all merges to follow agent-run synchronization, review, current-head CI and platform admission.
Evidence: Existing delivery stages and owner-only protection boundary reviewed; exact current Gitea Chinese labels verified from runtime resources.
Impact: Strengthen the merge executor rule only; retain human stage reviews, owner protection actions and actual CI requirements.
Refs: User instruction; merge-queue implementation plan U4/U5; Dev PR #519; Issue #518
Why: Close the delivered I1 task without modifying unrelated task records or shared workspaces.
Evidence: Dev PR 534 merged after all three exact-head CI jobs passed; RDM 360/362 and Documents 98/99 actual results and independent reviews are retained.
Impact: Archive this task card and preserve original receipts only; leave all worktrees, branches, production services and later IAM increments unchanged.
Refs: Dev PR 534; policy/delivery.md task closure authorization; IAM I1.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=e793e9804a1f5ecf49b29a40b4baac90ceb04e55.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Preserve independent final review and current-source equivalence before platform admission.
Evidence: Final document and integration metadata review has zero findings; full composition test and source equivalence receipts are retained with precise SELF object boundaries.
Impact: Delivery evidence only; no production, provider, guideline or document changes from the reviewed candidate.
Refs: IAM I1 integration task; Documents 98/99; RDM 360/362.
Why: Preserve actual component merge results and current delivery authorization before integration CI.
Evidence: RDM PR 360 merged at exact successful CI head; new Dev make test passed and independent metadata checks preserved approved digests and pins.
Impact: Clarify historical task records and current approved repair scope; preserve documentation and delivery evidence only.
Refs: Documents PRs 98 and 99; RDM PRs 360 and 362; IAM I1 task record.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=1e5c6b9c10ba77ed34663fd670138621a17342bd.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Carry the actual merged contract and approved permission implementation boundary into the integration composition.
Evidence: Documents PR 99 merged as a7ff466d9ae91fc67a53d2bf4991f47fc63a2a4c after independent review and verified source digest; RDM PR 360 preserves actual-actor projection semantics.
Impact: Update documentation pin, navigation and delivery records only; new composition tests and final-head CI remain required.
Refs: IAM I1 permission contract section 8; Documents PRs 98 and 99; RDM PR 360.
Why: the user confirmed acceptance in conversation on 2026-10-13; the archived
card should carry the verdict with an honest source label.
Evidence: user confirmation (conversation reply); automated ten-scenario replay
25/25 PASS rows on this card and PR #529.
Impact: archived task card note only.
Refs: task feature/rdm-increment-settings-duties (archived via #532).
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=5efbeebbdc09f8c2484613230a29c882c54652f0.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=5efbeebbdc09f8c2484613230a29c882c54652f0.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Record user acceptance and use the actual merged permission contract in the integration composition.
Evidence: Documents PR 98 merged as 3cf263962bd106529ee0531c8415cb16eecedfe3; independent document review and full SELF receipts retained in the task record.
Impact: Advance only Documents and delivery evidence; full IAM later increments and deployment remain outside scope.
Refs: Documents PR 98; IAM I1 U1-U2; policy/delivery.md stages 8-9.
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-rdm-increment-settings-duties.md(PR#529) — 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: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-d1-closeout-evidence.md(PR#517) — 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: include the current integration baseline before verification.
Evidence: fetched origin/main=5aae47ebca20ad1f3add3b080212cca7e1c6edf9.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Preserve the user-approved stage-7 conclusion before the final merge candidate is frozen.
Evidence: Import original precheck, sync, build, CI and independent replay receipts; validate current fixed components, document links and the incoming acceptance script syntax through make evidence.
Impact: Update this task card only; preserve implementation and activation boundaries. New HEAD CI remains required before merge.
Refs: Dev PR #519; Guidelines PR #5; Documents PR #96; queue Issue #518
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=5aae47ebca20ad1f3add3b080212cca7e1c6edf9.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=69c5c84d8a2f1a7966ebfb809cbb26d54e8e8abb.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=69c5c84d8a2f1a7966ebfb809cbb26d54e8e8abb.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Final fixed Documents composition and current modules passed their checks and now require the user acceptance decision.
Evidence: Complete SELF make test and document checks passed at4af5956; receipt5e81c91e and the independent RDM replay subjects are retained.
Impact: Record-only checkpoint after user stage 6 approval; do not claim stage 7 approval or shipping.
Refs: I1 bounded acceptance; policy/delivery.md
Why: Keep complete archive verification after the active card is moved.
Evidence: Original SELF synchronization and scoped diff receipts confirm no product or unrelated card changes.
Impact: Task records only.
Refs: Dev #526; RDM #354
Why: The approved base and downstream project membership delivery has reached its merge endpoint.
Evidence: Dev #526 and RDM #354 actual merge records, exact-head gates and independent reviews are preserved with original source labels.
Impact: Archive this task and record the separately authorized deployment follow-up; no product change, worktree cleanup or 8788 write.
Refs: Dev #526; RDM #354
Why: Keep the user-approved implementation and pending acceptance separate in the fixed integration records.
Evidence: Current Dev make test passed at10789653 and RDM combined checks passed at70e27b08; final text-only combination is verified next.
Impact: Documents and card records only; no permission source, pins in RDM, existing services or production data changes.
Refs: I1 stage 7 acceptance candidate
Why: task-sync flagged the earlier rows as recorded with uncommitted script
changes; the gate requires key checks re-run at a committed head.
Evidence: SELF row via make evidence - 25/25 PASS on a fresh rdm@84ca64f
disposable instance.
Impact: task card only.
Refs: task feature/rdm-increment-settings-duties.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ee9b437b22b49f96e1bc65f79417b22e8e82a37c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync