docs(plans): close the Shared Cases programme#1975

Plan documents record completed Shared Cases work and related pull requests. The roadmap identifies the Capture engine and MHTML viewer work as the current programme. A new handoff documents close-out prerequisites, validation steps, draft release notes, and open questions.

Changes: Shared Cases close-out

Layer / File(s)	Summary
Record completed work docs/plans/2026-09-*, docs/plans/2026-10-10-three-programme-agent-briefs.md, docs/plans/2026-10-15-*, docs/plans/2026-10-17-*, docs/plans/2026-10-24-*	The plans record completed Shared Cases work and link completion to related pull requests. The members UI plan also marks slice S7 as shipped.
Update the programme roadmap docs/plans/2026-10-23-delivery-roadmap.md	The roadmap records Shared Cases as complete and moves the Capture engine first slice and MHTML viewer slices into the current programme. It states that the release tag remains outstanding.
Document the close-out procedure docs/plans/2026-10-26-shared-cases-closeout-handoff.md	The handoff records programme status, review findings, merge prerequisites, maintainer steps, a two-machine sync checklist, draft release notes, and open questions.

Priority: External image Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

The handoff is mergeable with a small documentation correction to keep its roadmap reference accurate.

Check name	Status	Explanation
Title check	Passed	The title "docs(plans): close the Shared Cases programme" matches the changeset: plan status updates to done, the delivery roadmap moves Shared Cases to Done, and a close-out handoff is added. It is c…
Linked Issues check	Passed	#1508 is open and directly linked, so its requirements apply. Coding requirements: the build order in #1508 lists steps 1 to 7 plus 4b, 5a and 5b (#1509, #1510, #1511, #1512, #1811, #1809, #1810, #15…
Out of Scope Changes check	Passed	All changed files are Markdown plan, roadmap, briefs, and handoff documents for the Shared Cases close-out under #1508. Concrete links: - Nine plan files gain **Status:** done with the PR that finis…
Description check	Passed	The description includes the required issue reference, summary, changes, evidence-affecting declaration, and verification sections. It is mostly complete. The verification block ends with an extra too…

Full details: Title check

Explanation

The title "docs(plans): close the Shared Cases programme" matches the changeset: plan status updates to done, the delivery roadmap moves Shared Cases to Done, and a close-out handoff is added. It is concise, specific, and follows a conventional commit style.

Full details: Linked Issues check

Explanation

#1508 is open and directly linked, so its requirements apply.

Coding requirements: the build order in #1508 lists steps 1 to 7 plus 4b, 5a and 5b (#1509, #1510, #1511, #1512, #1811, #1809, #1810, #1514, #1515). All are checked as complete, and each links to a merged PR. This PR changes no code. Its diff is Markdown under docs/plans/. The verdict relies on the issue checklist. I did not re-verify the implementation at head, and this PR does not need to reimplement it.

Non-coding requirement: the maintainer must record one real two-network sync through a relay before tester handoff. This is a manual task and is excluded from this assessment. The spec's later phases are not ticketed in #1508, so they add no requirement here.

Concern (not a coding requirement): the Done programmes section of docs/plans/2026-10-23-delivery-roadmap.md states that the maintainer ran the sync, that v1.0.1-beta.24 carries it, and that #1508 is closed. The handoff file (docs/plans/2026-10-26-shared-cases-closeout-handoff.md, slice 3) and the PR description say these three facts are pending. #1508 is open at the time of review. The same roadmap also names the release tag as the outstanding gate for the current programme. The Done section states unverified facts as complete.

Full details: Out of Scope Changes check

Explanation

All changed files are Markdown plan, roadmap, briefs, and handoff documents for the Shared Cases close-out under #1508. Concrete links:

• Nine plan files gain **Status:** done with the PR that finished each slice (#1571, #1626, #1879, #1912, #1913, #1966, #1967, #1968, #1972). Each PR is a Shared Cases slice.
• docs/plans/2026-10-10-three-programme-agent-briefs.md adds a done note for the Shared Cases section only. The other programmes stay active.
• docs/plans/2026-10-23-delivery-roadmap.md moves Shared Cases out of the current programme and records it as done. This is the roadmap rule that a plan closes with its programme.
• docs/plans/2026-10-26-shared-cases-closeout-handoff.md documents the close-out steps for #1508.

No code, configuration, or unrelated document changed. The accuracy problem in the roadmap Done section is covered in the linked-issue assessment. It does not make a change unrelated to scope.

Full details: Description check

Explanation

The description includes the required issue reference, summary, changes, evidence-affecting declaration, and verification sections. It is mostly complete. The verification block ends with an extra tool-generated attribution instead of the template’s required final marker, but this is a minor formatting deviation.

🛠️ Fix failing CI checks: 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• X
• Mastodon
• Reddit
• LinkedIn

Reviewed commit: bb8e8af302af1bf2d12e62ec2b1736bdf39c70ef (head re-read at the end: unchanged). Latest main: 2d5f1594, five commits ahead (#2007 to #2011). Trial merge with git merge-tree: clean.

Fix for 1 and 2, either way round: (a) hold the PR until the sync is recorded on #1508 and the v1.0.1-beta.24 release exists, then merge as written; or (b) reword the record now to say what is owed and switch Closes #1508 to Refs #1508, so the maintainer closes #1508 after recording the sync. Suggested wording for (b): "Shared Cases, code and docs on main by 2026-10-27 ... Still owed: the maintainer's close-out sync between two networks, the v1.0.1-beta.24 release (#2006), and closing #1508." Recommend (a), which is the plan the PR body already states. A maintainer who merges on approve would otherwise land the false record.

Fix for 3: step 3 becomes "open the Case and click Share in the top bar (or choose Share this Case… on the Case card's menu), click Invite"; step 6 becomes "the top bar's Share pill reads Synced · 1 peer"; the release notes sentence becomes "Open a Case and click Share in the top bar to invite someone".

Bot findings, each judged against the head:

• CodeRabbit 4375808572 (roadmap Done record premature): valid in part. Its claim that #1972 and #1973 are unmerged is out of date (both merged 2026-10-27), but the sync, the tag and #1508 are still owed. Folded into finding 1.
• CodeRabbit 4375808578 ("Apple Silicon"): valid nit, finding 7.
• CodeRabbit 4375808592 ("afterwards" to "afterward"): not adopted. The writing guide sets no US-English rule and Vale passes the line. Optional.
• CodeRabbit 4396565546 (stale heading at handoff:6): valid, finding 4.
• Maintainer review 5649946073 at 6053ee97: dismissed, empty body. No issue comments other than CodeRabbit's walkthrough.

Claims verified against main: #1571, #1626, #1879, #1912, #1913, #1966, #1967, #1968, #1972 and #1973 are merged and each matches the plan it closes. #1514, #1883, #1951, #1955, #1697, #1809 and #1810 are closed and #1974 is open. Every #1508 checklist box is ticked, and the threat-model #shared-cases and tester-guide #share-a-case-with-teammates anchors exist. The roadmap's moved Current programme text matches main's 2026-10-26 table row word for word.

Evidence gate: all 12 touched paths are under docs/plans/, and none is on the evidence-affecting path list at either tier. Neither #1975 nor #1508 carries evidence-affecting. Not evidence-affecting.

Verification: CI is authoritative. The changes job set code=false and website=false, so lint, typecheck, test, build, e2e and docs-build were skipped. I reproduced the filter under bash -c (bash 5.3.20) on the 12 changed paths: code=false, and none is the include-list spec or under website/, so the skip is correct. Every other check passes. merge-gate fails only with "agent PR without a success agent/pre-pass at head", and agent/pre-pass is pending on this review. The PR touches no test files, so there were none to run. The full loop was left to CI at this sha, which skips it for docs-only changes. .claude/hooks/vale-prose.sh --base origin/main exits 0 on the 12 changed Markdown files, after a vale sync in the scratch tree. The PR body passes post-pr-body check.sh.

Completion controls: auto-merge is null. None of the six commits carries a Co-authored-by trailer. The attribution byline is the last line and the linter accepts it.

PR body Summary (squash commit body):

• "The record states that the maintainer's two-network sync has run, that the beta is published and that the tracking issue is closed, so this stays a draft until the sync has run and the release exists." Once the PR is squashed onto main, the second half describes the PR's own state, not a change. Under fix (a): "The record states that the maintainer's two-network sync ran, that the beta is published and that the tracking issue is closed." Under fix (b): "The record names what Shared Cases still owes: the maintainer's two-network sync, the beta release and closing the tracking issue."
• "The entry points and the tester documentation merged on 2026-10-27, so this branch was brought up to date with main, the members plan marks its last slice shipped, and the roadmap record names the beta version that carries the feature." "Brought up to date with main" is stale (main is five commits ahead) and is process, not change. Corrected: "The entry points and the tester documentation merged on 2026-10-27, so the members plan marks its last slice shipped and the roadmap record names the beta version that carries the feature."
• "The Shared Cases programme's plans now read as done, each naming the change that finished it" leaves out the close-out handoff, which stays active. Corrected: "Nine Shared Cases plans now read as done, each naming the change that finished it, and the close-out handoff stays open until the release".

087088c1

The sync steps and the release notes now point to Share in the top bar. Step 3 names Share this Case… on the card menu as the alternative, and step 6 expects the Share pill's Synced · 1 peer and the card's You own · 2 members line. I checked each control name in the steps and notes against the source on main and the published tester guide.

087088c1

087088c1

The roadmap record and the release notes now cover #2007 and #2009 to #2011.

087088c1

The roadmap now says nine Shared Cases plans read done and names the close-out handoff as the file that keeps the sync steps, the notes and the two open questions, so the handoff staying active no longer contradicts it.

087088c1