Why: Final review and real composition exposed member upload rejection, private project cards and stale duty selection.
Evidence: Component correction receipts and fixed clean source SHAs; independent replays and final composition are in progress.
Impact: Select Backend d2f96e7 and Frontend 2ba275b with current UI, preserving private originals and verified project commands.
Refs: feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=86d975b822c2384e96edd75f9c3a2dca63593b3a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Host-only project creation and domain membership must form one verified identity.
Evidence: Tool-imported SELF receipts and independent Backend and Frontend replay attestations; composed acceptance and final CI remain in progress.
Impact: Advance fixed component pins and record the authorized implementation and privacy boundaries without deployment or runtime changes.
Refs: .task/feature-project-member-access.md; system-project-membership proposal r1
Why: retain the repeatable membership check and current integration checkpoint.
Evidence: SELF receipts in the task card; readiness fails on the reported data state.
Impact: diagnosis metadata only; product implementation remains pending stage review.
Refs: .task/feature-project-member-access.md
Why: a saved host-project membership has no registered RDM project or binding,
so member discovery and private conversation creation cannot resolve it.
Evidence: metadata-only read probes and forge scans are preserved as SELF
receipts in the task card; HTTP and browser replay remain NOT_RUN.
Impact: task documentation and read-only diagnostic helpers only; product
code, runtime databases and deployments are unchanged pending stage review.
Refs: .task/feature-project-member-access.md; policy/delivery.md
Why: the task card needs the pull request that carries this closeout, and the review has to name the commit it actually read.
Evidence: reviewed 814451b1fc8435a92ef7b29ac4fe8480a330c3b1; pull request 517.
Impact: task metadata only.
Refs: .task/feature-d1-closeout-evidence.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=55cecae703cf8c4f33185e9e4556597c11817b3b.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: the archived D1 card still marked merge, CI, and lifecycle as NOT_RUN after the four pull requests had landed.
Evidence: Gitea runs 2625, 2631, and 2667; make test-lifecycle receipt 1a4650d89e589321 (SELF, exit 0 on 2df298affe).
Impact: task cards only. Login, rdm.ping, and the full-track deploy stay NOT_RUN.
Refs: .task/archive/feature-svc-d1-identity-flow.md .task/feature-d1-closeout-evidence.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-project-member-access.md; R0=55cecae703cf8c4f33185e9e4556597c11817b3b.
Impact: task metadata only; the feature workspace starts at 55cecae703.
Refs: .task/feature-project-member-access.md
Why: The login recovery contract reserved the owner browser login step
for the user (passwords never pass through the agent); the user
confirmed the test passed on 2026-10-13, closing the final acceptance
loop.
Evidence: User session confirmation 2026-10-13; deploy and prior
verifiable acceptance under receipt 5396054b.
Impact: Doc-only status update in the leftover section.
Refs: docs/svc-deploy/2026-10-13-login-recovery-contract.md.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-d1-closeout-evidence.md; R0=c39321ab7bae6e618f13ec2b48df7abf89d44604.
Impact: task metadata only; the feature workspace starts at c39321ab7b.
Refs: .task/feature-d1-closeout-evidence.md
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#502) feature-svc-account-hardening.md(PR#511) — 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 dropped RDM DHF document templates at .templates/ for
upcoming use and wants them synced through the repository instead of a
local ignore; the temporary .gitignore entry is reverted and .DS_Store
junk is excluded.
Evidence: 44 template files staged (18MB, .doc/.docx across DHF stages);
.DS_Store ignored; working tree clean after staging (owner-directed
disposition of these files per session instruction).
Impact: Data-only addition under .templates/; .gitignore gains
.DS_Store; no code paths touched.
Refs: User instruction 2026-10-13 (templates to be used later).
Why: The remaining open items (API-key SSE closure, cross-instance
redeem backoff, U7 atomic bootstrap/create, CLI credential delivery)
landed in Backend #192; Dev pins it and closes the contract leftovers.
Evidence: Backend #192 CI success at head bc1e0a3 (GATE); composite CI
on this PR re-runs the suite incl. test-pg (GATE).
Impact: backend pin cfb8308; contract leftover section now records all
items closed; task card H1-H6 requirement table.
Refs: Backend #192; docs/svc-deploy/2026-10-13-login-recovery-contract.md.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-svc-account-hardening.md; R0=3e5416a8226c2dfdd108d6282566639c2ed41f1e.
Impact: task metadata only; the feature workspace starts at 3e5416a822.
Refs: .task/feature-svc-account-hardening.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-svc-login-recovery-flow.md(PR#504) — 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 D3 real-scenario card is merged and must leave the open set.
Evidence: CI on aa5d0512bf35d1a860dea2a44b98bddcd8e2364e; ci/test, ci/test-pg, ci/svc-realcombo success.
Impact: archives only this card. Login and rdm.ping stay NOT_RUN.
Refs: .task/archive/feature-svc-d3-real-scenarios.md
weichen
