Why: Preserve authoritative settings and session changes with the source-bound work candidate.
Evidence: Merged Backend, Core and live fixture guards passed local and independent checks; extra A01 remained a real FAIL.
Impact: Save a draft-reviewable composition without claiming CI, merge, deployment or model-quality approval.
Refs: U2/U3 task card and validation report
Why: Continue the existing delivery after explicit approval for one extra sample.
Evidence: Startup precheck READY and live output/run-limit fixture checks are recorded by evidence.
Impact: Fixed evaluation candidate, max two paid runs and no automatic retry; preserve all original failed samples.
Refs: User approval 2026-10-13
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=719bfe945f46d43a22d7ac7025d2313faa4bf0e4.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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: Preserve a clean reviewable candidate without treating code checks as a passed model gate.
Evidence: Native receipts retain final combination, PostgreSQL and actual HTTP/browser verification; independent code review is archived in Documents.
Impact: Save documentation and evidence, retain registered worktree and unmerged branches pending the requested extra test authorization.
Refs: U2/U3 plan r0.1 and validation report
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 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: include the current integration baseline before verification.
Evidence: fetched origin/main=d40d1c2e5d29bb0ce429edf2221d9c4e4bcb0dcb.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Keep the implementation, honest failed model evidence and approved planning progress reviewable as one candidate.
Evidence: Native SELF suite, PG and meaningful red-to-green receipts; independent reviewer reports and all original model artifacts are retained.
Impact: Pin source-record and terminal-state fixes; preserve U3 acceptance and extra-sample authorization as pending, with no deployment.
Refs: Approved U2/U3 plan and validation report
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>
Why: depth 1 makes prev_sha and sha unrelated shallow roots, so update reports a fork instead of an upgrade.
Evidence: SELF the pin-fetch credential test; CI run 2829 showed the fork message.
Impact: test-pg fetches 200 commits from each pin, not the full history.
Refs: .task/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=268ef2999ca2ff3481c6bebd588cae51d6b90709.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Keep the accepted login recovery release and U2/U3 fixes in one current composition.
Evidence: Exact incoming Backend 467718a and Frontend 9fc7da2 were fetched and merged without source conflicts; task-sync receipts retain the gitlink conflict.
Impact: Preserve both component histories and refresh the authoritative base before final combination checks.
Refs: origin/main 268ef299; feature-fast-slow-u2-u3-plan
Why: the CI fix needs a tool-written receipt on the commit that contains it.
Evidence: SELF make evidence, exit 0.
Impact: task metadata only.
Refs: .task/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Resolve the observed conclusion and qualification defects without rewriting failed evidence.
Evidence: Native SELF model failure and red-to-green conclusion receipts are retained in the task card.
Impact: Candidate recipe changes; an A01 rerun remains outside the original six-sample authorization.
Refs: Approved U2/U3 plan r0.1
Why: Merge requires the current head CI result on the task card, with the run link, executor, and SHA.
Evidence: Run 2821 attempt 2 on head 3090dd9 has test, test-pg, and svc-realcombo success on home-runner (GATE). Attempt 1 failed in an unrelated timing-sensitive governance test and was rerun.
Impact: Task card only. Second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Preserve complete receipts before requiring a clean sync workspace.
Evidence: Native SELF outputs include the green corrected PG suite and remote refresh retries.
Impact: Evidence only; implementation pins remain unchanged.
Refs: feature-fast-slow-u2-u3-plan
Why: Complete the approved U2/U3 fix pass and prevent shared host fixture collisions.
Evidence: Native SELF receipts record complete Backend suite, Frontend 221 tests, meaningful startup regression failures and the bounded baseline model batch.
Impact: Pin the corrected Backend and Frontend and allocate owned recovery fixture ports; no existing service deployment.
Refs: modules/documents/docs/proposals/2026-10-13-fast-slow-u2-u3-plan.md
Why: The Dev composite must carry the exact backend (467718a) and
frontend (9fc7da2) commits implementing the login recovery contract.
Evidence: component branches pushed to their origins; make test runs in
this task worktree validate the composite (receipts in task card).
Impact: gitlink bump only; no other Dev tree changes.
Refs: docs/svc-deploy/2026-10-13-login-recovery-contract.md
Why: The 2026-10-13 login flow plan requires a frozen contract record
(three adjudications against the r2 proposal) and a traceable task card
before implementation merges.
Evidence: doc-only commit; acceptance matrix cites backend/frontend test
files added in companion commits (SELF).
Impact: docs/svc-deploy/2026-10-13-login-recovery-contract.md becomes
the authoritative login-recovery contract; task card records user
authorization and requirement table L1-L9.
Refs: modules/documents/docs/proposals/2026-10-12-svc-unified-deploy-and-login-key.md r2
Why: the card's main record must point at the review object before CI is accepted.
Evidence: PR 503 exists on the current branch.
Impact: task metadata only.
Refs: .task/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the sync checkpoint must be a tool-written receipt on the same card as the tests.
Evidence: SELF CMD make task-sync, exit 0, sync_base 3fb8210f64.
Impact: task metadata only.
Refs: .task/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: completion claims need tool-written receipts, including the SSH timeout and the passing rerun.
Evidence: SELF make evidence rows on this card.
Impact: task metadata only; login and rdm.ping stay NOT_RUN.
Refs: .task/feature-svc-d3-real-scenarios.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The merge step requires a fresh sync against origin/main recorded on the task card.
Evidence: make task-sync exit 0; sync_base 3fb8210f, tested_head d3f8677, already up to date (SELF).
Impact: Task card only.
Refs: .task/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The merge gate needs a review record on the task card for the PR head.
Evidence: Review of base 3fb8210f against head dd77d27 found docs and the task card only, unchanged evidence grades, and no secrets. No blockers.
Impact: Task card only. Second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Acceptance needs the task-sync and make test outputs on the task card before the PR. The first make test failed because an unrelated process held port 18795; the rerun passed.
Evidence: make task-sync exit 0 against origin/main 3fb8210f (SELF). make test exit 0 after the port was freed (SELF). CI on the PR head remains the authority.
Impact: Task card only. Evidence grades are unchanged and second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.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-svc-login-recovery-flow.md; R0=3fb8210f6495a78e70a67af3661bdfe9c00fb9de.
Impact: task metadata only; the feature workspace starts at 3fb8210f64.
Refs: .task/feature-svc-login-recovery-flow.md
Why: The user authorized continuous delivery of the release-gate specs through merge and task-card closeout. The card still said no continuous authorization and left stages 1-6 unreviewed.
Evidence: Startup precheck READY, receipt imported into the task card (SELF). Spec claims rechecked locally: tree equality holds, policy/facts.md and the Documents repo are untouched, and checklist grades stay SELF or not started.
Impact: Task card text only. No replay, no workflow change, no second host, and second-instance writes stay closed.
Refs: .task/feature-u7-release-roadmap.md
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
