Records the remaining U7 release gates as executable specs: independent replay (docs/u7-release-replay.md), CI fast-lane feasibility (docs/u7-release-ci-feasibility.md), and the second-host checklist (docs/u7-release-c3-host.md).
The checklist docs/release-multi-instance.md gains a pointer section. Evidence grades stay SELF or not started. C4/C5 are not promoted, C3 stays not started, and second-instance writes stay closed.
Docs and the task card only. policy/facts.md, .gitea/workflows/ci.yaml, and the Documents repo are untouched. The collaboration proposal body stays r2.3; the r2.4 sentence is quoted in the checklist and not written to Documents.
Task card
Progress, authorization, and the precheck / task-sync / test evidence live in .task/feature-u7-release-roadmap.md (source SELF). The authoritative test result is CI on this PR head.
Test plan
CI on the PR head: test, test-pg, svc-realcombo all success, and the run SHA matches the head
Review confirms the diff is docs-only and does not raise any evidence grade
Merge commit tree equals the PR head tree (git rev-parse ^{tree})
## Summary
- Records the remaining U7 release gates as executable specs: independent replay (`docs/u7-release-replay.md`), CI fast-lane feasibility (`docs/u7-release-ci-feasibility.md`), and the second-host checklist (`docs/u7-release-c3-host.md`).
- The checklist `docs/release-multi-instance.md` gains a pointer section. Evidence grades stay SELF or not started. C4/C5 are not promoted, C3 stays not started, and second-instance writes stay closed.
- Docs and the task card only. `policy/facts.md`, `.gitea/workflows/ci.yaml`, and the Documents repo are untouched. The collaboration proposal body stays r2.3; the r2.4 sentence is quoted in the checklist and not written to Documents.
## Task card
Progress, authorization, and the precheck / task-sync / test evidence live in `.task/feature-u7-release-roadmap.md` (source SELF). The authoritative test result is CI on this PR head.
## Test plan
- [ ] CI on the PR head: test, test-pg, svc-realcombo all success, and the run SHA matches the head
- [ ] Review confirms the diff is docs-only and does not raise any evidence grade
- [ ] Merge commit tree equals the PR head tree (`git rev-parse ^{tree}`)
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-u7-release-roadmap.md; R0=3fb8210f6495a78e70a67af3661bdfe9c00fb9de.
Impact: task metadata only; the feature workspace starts at 3fb8210f64.
Refs: .task/feature-u7-release-roadmap.md
Why: Second-instance writes stay closed until an independent replay or an admitted CI gate, plus a second host. Those remaining steps needed a durable spec.
Evidence: Task-card evidence rows read the merged PRs, tree equality, CI runs 2783/2810/2816, and Dev main branch protection. Source SELF. Drills were not run.
Impact: Docs and the task card only. Checklist grades stay SELF or not started. The collaboration proposal body stays r2.3.
Refs: docs/release-multi-instance.md
Co-authored-by: Cursor <cursoragent@cursor.com>
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>
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: 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: 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: 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: include the current integration baseline before verification.
Evidence: fetched origin/main=268ef2999ca2ff3481c6bebd588cae51d6b90709.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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
merged commit d40d1c2e5d into main2026-10-13 04:22:58 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
docs/u7-release-replay.md), CI fast-lane feasibility (docs/u7-release-ci-feasibility.md), and the second-host checklist (docs/u7-release-c3-host.md).docs/release-multi-instance.mdgains a pointer section. Evidence grades stay SELF or not started. C4/C5 are not promoted, C3 stays not started, and second-instance writes stay closed.policy/facts.md,.gitea/workflows/ci.yaml, and the Documents repo are untouched. The collaboration proposal body stays r2.3; the r2.4 sentence is quoted in the checklist and not written to Documents.Task card
Progress, authorization, and the precheck / task-sync / test evidence live in
.task/feature-u7-release-roadmap.md(source SELF). The authoritative test result is CI on this PR head.Test plan
git rev-parse ^{tree})