J87: keys and lifetimes doc, and docs searchable in the palette #301

New issue

Closed

opened 2026-11-02 04:36:24 +00:00 by kayg · 1 comment

kayg commented

2026-11-02 04:36:24 +00:00

Owner

Job J87 (UI + docs). Two deliverables, two kinds of commit:

docs/keys.md, "Keys and how long they last": one table, then one short paragraph per key (what it is, where it lives, when it expires or rotates, what happens offline). Sources are cited as decision numbers in the footer: the key-lifetime table on #269 (comment 72638), #285, #221 Q6, #263, D311. Every claim is checked against origin/dev; where the code and the decision differ the page says what the code does today and the difference is flagged here.
The docs in the ⌘K palette: the page and heading titles of the docs build (#298) become a palette source. The index is a tiny JSON emitted by the docs build and fetched on the first palette open (on demand, not in the critical JS). Enter opens the page in the canvas as a window (the existing flow-window host), not a browser tab.

Plan and estimate

Read-through of the code for each key (auth, mesh, setup code, recovery, api keys): 45 min
docs/keys.md + docs build registration + findings on this issue: 45 min
Palette source + docs search index (build step) + reader window: 75 min
Unit tests + Playwright on a production build (search, open, ±0.5 px, phone) + screenshots: 60 min
Gate on a VM + report: 30 min
Total about 4 h 15 min; I stop and report at 8 h 30 min.

Out of scope (scope leash): full-text search, a docs site framework, a new window kind beyond what the flow host already provides, any change to key lifetimes in code.

Branch docs-keys-palette from origin/dev 9f36dd8e0a.

Owner (2026-11-02): "what sort of keys do we have and which expire when? again i want this to be documented. and should docs be just another part of the canvas searchable by cmd k?" (the orchestrator recommends yes). Job J87 (UI + docs). Two deliverables, two kinds of commit: 1. `docs/keys.md`, "Keys and how long they last": one table, then one short paragraph per key (what it is, where it lives, when it expires or rotates, what happens offline). Sources are cited as decision numbers in the footer: the key-lifetime table on #269 (comment 72638), #285, #221 Q6, #263, D311. Every claim is checked against origin/dev; where the code and the decision differ the page says what the code does today and the difference is flagged here. 2. The docs in the ⌘K palette: the page and heading titles of the docs build (#298) become a palette source. The index is a tiny JSON emitted by the docs build and fetched on the first palette open (on demand, not in the critical JS). Enter opens the page in the canvas as a window (the existing flow-window host), not a browser tab. Plan and estimate - Read-through of the code for each key (auth, mesh, setup code, recovery, api keys): 45 min - docs/keys.md + docs build registration + findings on this issue: 45 min - Palette source + docs search index (build step) + reader window: 75 min - Unit tests + Playwright on a production build (search, open, ±0.5 px, phone) + screenshots: 60 min - Gate on a VM + report: 30 min Total about 4 h 15 min; I stop and report at 8 h 30 min. Out of scope (scope leash): full-text search, a docs site framework, a new window kind beyond what the flow host already provides, any change to key lifetimes in code. Branch `docs-keys-palette` from origin/dev 9f36dd8e0a5e9e799cd3264cb6e1e7605071c5e2.

kayg commented

2026-11-04 17:04:54 +00:00

Author

Owner

J210 owner-authorized housekeeping: closing this duplicate record as superseded by #302, which tracks the same work and retains its implementation/evidence. This closure does not assert that all successor follow-ups are complete.

J210 owner-authorized housekeeping: closing this duplicate record as superseded by [#302](https://git.kayg.org/kayg/infraternal/issues/302), which tracks the same work and retains its implementation/evidence. This closure does not assert that all successor follow-ups are complete.

kayg closed this issue

2026-11-04 17:04:54 +00:00

kayg referenced this issue

2026-11-04 17:07:06 +00:00

J210: overnight housekeeping, 2026-11-04 #350

No labels

launch-qa

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kayg/infraternal#301

No description provided.

Rows
Columns