Repository navigation
docs: the M12 record — a tailnet login that lasts until the token is rotated, and the roadmap row (#230) - #237
Conversation
…rotated, and the roadmap row (#230) This is the milestone record on the housekeeping path (SPEC section 4): docs/milestones/12-a-tailnet-login-that-lasts.md, the M12 row in ROADMAP.md, and the front-door claims M12 changed. The introduction's opening describes the project at the end of milestone twelve, with a paragraph on what M12 changed, and its suite count goes from 120 to 123; CONTRIBUTING lists openssl for the tailnet session suite and counts twelve suites and 123 tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The milestone record on the housekeeping path. The coordinator's Decision on where the operator's words came from (#230, 5910571213) now backs the gate resolution, the manual link and the wait for it, the relayed scope ("ov v0.3.1", quoted corrected), the upstream-capture ask and the tool-written operator confirmation. The record keeps that the attribution was posted late, at record time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review — 1d8a237Reviewer seat ( Findings1. nit: the PR body contradicts the record it carries. Its Gaps the record names section says "Unlike M11, no attribution comment is on the trail for the operator's session words. The record gives the attributions as the coordinator relayed them to this seat and says so". That was true of 2. nit: an unwrapped line in the introduction. 3. nit: the manual-link wait is stated more strongly than its source. 4. nit: two claims in The hand-close cite a comment that does not carry them. 5. nit: "the Decision corrected it" is ambiguous. At 6. nit: one of the #39 quotes is not verbatim. At 7. nit: the sync guide is misquoted in the front-door section. Nothing blocking. What I verified, and how
Capture candidatesNone. Verdict: approve |
The milestone record on the housekeeping path. The introduction's suite paragraph is reflowed. The record says the task waited on the manual link, with cf8d515 the one other event in that window; cites radiusred/gh-codecrew#386 for the "closes via its closing keyword" output and how the hand-close was noticed; says the scope Decision quotes "ov" with "of"; restores "either" in the #39 quote; and quotes the e-ink and sync guides each on its own terms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Operator confirmation: this record, at head 9a38e03, is accepted for the operator (pure solo tier, SPEC §4). The acceptance rests on his standing merge confirmation for this milestone and its record ("run it through to a release"), recorded in #230 (comment) and relayed from the coordinator session, per #230 (comment). The model review approved at 1d8a237 (#237 (comment)). Commit 9a38e03 takes all seven of that review's nits, which are wording and line wrapping only. The gate passed; |
The M12 record, on the housekeeping path (SPEC §4). Milestone: #230. This PR does not close it;
gh codecrew milestone close 12does.What this adds
The record:
docs/milestones/12-a-tailnet-login-that-lasts.md. It covers the goal and outcome, the stateless signed cookie against a persisted store with the Tailnet access: extra Host name, token login and session cookie #39 rejections it reverses, the idle-limit gate and its 30-day answer, the addendum (a restored token revives its sessions; a refreshed cookie gets a new id), the three PRs (fix(session): a tailnet login survives restarts and ends on rotation (#231) #232, fix(session): a tailnet login survives restarts and ends on rotation (#231) #233, fix(session): a tailnet login survives restarts and ends on rotation (#231) #234) and GitHub's failure to link and to close Tailnet sessions that survive restarts and end on rotation #231, the manual link and the hand-close, the requirement outcomes, QA's findings and their disposition, the captures (A tailnet login should last until the token is rotated, not end at every daemon restart #229 adopted; Pin the tailnet session format and 'no secret at rest' with tests #235, An e2e test that installs the app for real and checks it stays logged in #236 and Backlog capture: task finish says the task closes but never checks that it did radiusred/gh-codecrew#386 raised), and the v0.3.1 release plan, to be tagged aftermilestone close 12.The roadmap row for M12, already Done.
Front-door claims M12 changed:
docs/introduction.md: the opening now describes the project at the end of milestone twelve, a paragraph says what M12 changed, and What holds these numbers counts 123 browser checks (was 120) and names the tailnet session suite and itsopensslneed.CONTRIBUTING.md: What you need listsopensslfor that suite, and themake e2eparagraph counts twelve suites and 123 tests (was eleven and 120).The introduction's A browser on the tailnet,
docs/running.mdandcontrib/mdn.1were updated by Tailnet sessions that survive restarts and end on rotation #231. The README makes no claim M12 changed.Gaps the record names
The coordinator's attribution Decision on #230 (where the operator's words came from) exists, and the record cites it for each attribution. It was posted late, at record time, and the record says so under Where the record is silent.
Checks
gh codecrew milestone evidence 12: requirements M12-R1 to R5 counted, all 6 cited links on the trail resolve. The record is not onmainyet, so each of its 35 distinct github.com links was also resolved withgh api, and each comment link checked to belong to the issue or PR it names.make checkexits 0.🤖 Generated with Claude Code