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: 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
Why: the branch is on main, so this card must leave the open set without closing unrelated cards.
Evidence: merge 719bfe945f46d43a22d7ac7025d2313faa4bf0e4; CI run 2853 success on 424892258b.
Impact: task metadata only. Login and rdm.ping stay NOT_RUN.
Refs: .task/archive/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the runnable D3 scenarios now execute against real RDM artifacts.
Evidence: CI run on 424892258b19a8bdd1c9dd430d89334ea0cafa78; ci/test, ci/test-pg, ci/svc-realcombo success.
Impact: login and rdm.ping stay NOT_RUN.
Refs: .task/feature-svc-d3-real-scenarios.md
Why: check-pins failed on the follow-up CI: the newly pinned backend
(741da4a) carries deps/agent-system-core at 0f94e4b while Dev's
modules/core stayed at ba289e7 - the three-layer pin rule requires the
top-level core pin to match.
Evidence: 0f94e4b verified as an ancestor of Core origin/main; this
PR's composite CI re-runs check-pins (GATE).
Impact: modules/core gitlink to 0f94e4b; no source changes.
Refs: check-pins failure on job 4204.
Why: The follow-up CI exposed that backend #188 broke the Dev
multi-instance suite: serve --mock seeded runtime.mock at the user
scope, which system-managed settings now reject, so instances never
became healthy. Backend #190 seeds the startup flag into the system
scope; this PR repins and drops the now-invalid alice user-scope write.
Evidence: Backend #190 CI success at head 0af1ebc (GATE); this PR's
composite CI re-runs make test-multi-instance (GATE for the fix).
Impact: backend pin 741da4a; multi-instance test comments updated to
the system-managed regime.
Refs: Backend #188, #190.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=6fd51fec9fed2a95f51420d2c1a8bd5d82db2ae6.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The completion audit flagged four gaps over the merged login
recovery implementation: real-browser acceptance, the login-key e2e
spec, SSE stream invalidation, and the Documents write-back.
Evidence: Browser acceptance receipts be7ae9a2/b3a9e691 (SELF, bound to
Dev HEAD 268ef29); Backend #189 CI success at head 8b73afe (GATE);
Documents #94 merged; this PR's composite CI is the GATE for frontend
pin 44b9646.
Impact: Pins backend=349a47d (SSE close) and frontend=44b9646 (e2e
spec); contract doc leftovers updated; task card carries the follow-up
record for closure.
Refs: docs/svc-deploy/2026-10-13-login-recovery-contract.md; Documents
proposal r3; Backend #189; Frontend #77.
Why: The merge record was committed after PR 501 merged, so the closeout archived the card without it.
Evidence: The two lines match commit 2771196 on the task branch. Run 2832 on head 72763c9 passed, and merge d40d1c2 has the same tree.
Impact: Archived task card text only. Second-instance writes stay closed.
Refs: .task/archive/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The specs branch merged, but its merge subject lacks the default branch tail, so the close scan did not select this card.
Evidence: merge d40d1c2 of PR 501 is in origin/main and its tree matches head 72763c9. Backfill follows the card_backfill format.
Impact: One task card moved to .task/archive with status backfilled. No code change. Second-instance writes stay closed.
Refs: .task/archive/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d40d1c2e5d29bb0ce429edf2221d9c4e4bcb0dcb.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The remaining U7 release gates needed a durable spec before anyone replays them or wires CI.
Evidence: Run 2832 on head 72763c9 has test, test-pg, and svc-realcombo success on home-runner. Review found docs only and unchanged evidence grades.
Impact: Docs and the task card. Checklist grades stay SELF or not started. Second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.md
Why: Main advanced with the login recovery merge while CI was running, so the branch had to take it in before merge. The new combination needed its own test evidence.
Evidence: make task-sync merged origin/main 268ef29 with no conflicts (SELF). make test exit 0 on the merged tree (SELF). CI on the new head is still required before merge.
Impact: Task card plus the merge of main. The release specs are unchanged. Second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
