Docs: 1.0 release-readiness working doc + dashboard#906
Conversation
The working documents that steered the Tue–Thu release-verification push, kept current through the week: - RELEASE-READINESS.md — the source of truth: 10-gate ship checklist with per-gate status and burndown, the locked decisions (D1–D6), rule-family and overlay-sidebar inventories, the findings log (Mapper claims, #881 restore data loss, CI fake-green lane, leader-picker probe), gate-6 triage results (must-fix list closed empty), and the known-limitations release-notes draft. - RELEASE-READINESS.html — self-contained visual dashboard of the same state: ship-gate table, verdict card, burndown chart with the Wed-night scope-add jump, coverage donut, inventories, and findings timeline. No external dependencies; opens offline. Both are point-in-time working artifacts for the 1.0 cycle rather than evergreen docs; they live at the repo root alongside CODE_AUDIT.md, which set the precedent for cycle-scoped reports. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…n-track Gate table: 6 closed (4, 5, 6 closed Thu; 6 closed EMPTY a day early), 9 nearly closed, 7/10 scheduled. Verdict card green: ~10h remain vs ~16+ available. Burndown extends the actual line through Thursday's ~21h close-out and the projection reaches zero before Saturday's RC. Schedule strip marks Thu done, Fri next.
- Gate-6 table row now matches the 'CLOSED EARLY (Thu PM)' section (codex P2 + claude review points 1-2): closed, must-fix empty. - 'Days remaining: 5' rotted on day one — replaced with an absolute 'Last updated' field (review point 3). - Gate-9 'Open question' about the orange box now records the D6 resolution (#893) instead of sending readers ghost-chasing (review point 6). HTML was already synced by the prior dashboard commit.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 026e623fc8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <h1>KeyPath 1.0 — Release Readiness</h1> | ||
| <div class="sub"> | ||
| <span class="dot"></span> | ||
| <span>End of Thu 2026-06-11 — triage closed EMPTY a day early · 6 of 10 gates done · RC staged for Sat</span> |
There was a problem hiding this comment.
The HTML dashboard says the end-of-Thu state is “6 of 10 gates done,” with triage closed and RC staged, but the linked markdown source in this same commit still says “Thu AM,” “4 of 10 gates closed,” an at-risk hours gap, and even lists Thu work as “next.” Since this file is presented as the release-readiness status page, readers can’t tell which release gate state is current; please regenerate or edit one source so the dashboard and markdown agree before using it for the ship decision.
Useful? React with 👍 / 👎.
Code Review — PR #906: Docs: 1.0 release-readiness working doc + dashboardOverviewDocs-only PR adding two files: What's good
Issues1. HTML footer says "Auto-synced" but it is a hand-maintained snapshot (misleading) The footer reads:
The second and third clauses contradict each other — "Auto-synced" implies the HTML updates automatically, but the third clause says to update by hand. The PR description even notes "the HTML carries a hand-synced-snapshot caveat," but the actual footer text does not deliver that caveat clearly. Suggested fix:
2. HTML is one day behind the Markdown
The most significant Thursday development — Gate 6 closing early with an empty must-fix list — happened after the HTML was last updated. Readers who open the dashboard will see a different status than readers who open the Markdown. Either sync the HTML before merge or add a visible "this snapshot may lag the .md file" callout to the dashboard header. 3. Hero section has a pulsing-green "live" dot The dashboard hero includes a green glowing dot styled like a live-status indicator. Combined with the "Auto-synced" footer text, this reads as a live dashboard. Once "Auto-synced" is corrected to "snapshot," the dot is purely cosmetic and fine — just worth being aware of if the dashboard gets shared for stakeholder communication. Minor notes
VerdictApprove with suggestions. Issues 1 and 2 are low-stakes but worth fixing before merge since the dashboard is likely to be shared during the final stretch. Neither blocks merge if you want to land this now and update the HTML in a follow-up, but the footer text fix is a one-liner. |
1 participant
Replaces the docs half of #899 on a clean branch. #899's branch turned out to be shared with another in-flight workstream (the kanata
cmdremoval landed on it mid-review, making the "docs only" description wrong) — this PR carries only the two documentation files, and #899 is being re-pointed at the security work it actually contains.What's here
RELEASE-READINESS.md — the working doc that steered the Tue–Thu 1.0 verification push: 10-gate ship checklist with burndown, decisions D1–D6, rule-family + overlay-sidebar inventories, the findings log (#881 restore data-loss saga, CI fake-green lane, Mapper claims, leader-picker probe), gate-6 triage (closed Thursday with an empty must-fix list), and the known-limitations release-notes draft.
RELEASE-READINESS.html — self-contained visual dashboard of the same state (inline SVG, renders offline).
Review feedback from #899 — addressed here
CODE_AUDIT.mdcycle-report precedent (point 4); the HTML carries a hand-synced-snapshot caveat in the PR description per point 5showDebugBordersetc.) is queued for a post-1.0 cleanup note rather than this PRDocs only — verifiably this time: two files, no code paths.