Repository navigation
docs(rfc): mark the Living UI RFC implemented - #22712
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS This is a docs-only update to RFC status, and it follows a recorded maintainer decision. It adds no behaviour, surface or take-away, so there is nothing at design level to check. [DESIGN-REVIEWED] d248b0e Description read[DESCRIPTION-READ] a9aaacd1874128ce4f01ca4ff6c9f263e6188cc3fe9c08f3457dccef3f905563 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
a2cd99d to
d248b0e
Compare
|
RFC update to show the latest implementation status |
Problem / Motivation
Goal: The Living UI RFC and the RFC index say what is on main: the RFC is accepted and implemented.
docs/request-for-change/rfc-living-ui.mdstill saysstatus: draftand "Nothing is built", and its README index row says the same. Every required row of its §11 plan has merged since.Why it matters
A reader, or the First Principles lane, reads the status field to learn what is decided and built. A stale
draftsays the opposite of main.Not a goal
What changed (motivation → approach → change)
The maintainer decided, so the record follows. In the conductor chat on 2026-10-21 at about 08:25 UTC, the maintainer iamwhatever wrote: "我接受,开记账 PR 改成 implemented" (I accept; open the bookkeeping PR and mark it implemented).
rfc-living-ui.mdfront matter:status: implemented,implementation-prslists the eleven PRs,last-audited: 2026-10-21,audited-at: 0b89e0c6f7.- Status:line says who accepted it, when, and which PR carried each §11 row. Row 9 is marked optional and not done.9d088c85ad.README.md: the index row isimplementedwith what shipped, PR links andverified at 0b89e0c6f7. The header log gets one clause for the move, matching the other moved rows.SKILL.mdreadout,focusOnetourexplodeRow 9 (measure, then decide on injection) is optional and not done.
Each PR above is merged, its merge commit is an ancestor of
0b89e0c6f7, and every file it touched exists there.Backwards compatibility
Compatible: two Markdown files change; no code reads the RFC status text.
Removes nothing: only status and wording lines change; no file, row or anchor goes away (no link targets
rfc-living-ui.md#...).Tests
N/A — docs only.
python3 scripts/docs_lint.pypasses, andtest/test_docs_lint_fact_checks.pypasses (98).Manual verification
Checked each PR with
gh pr view(state MERGED) andgit merge-base --is-ancestoragainst0b89e0c6f7, and checked every file each PR touched is present.Related Issues
Closes #21796 — every required §11 row has landed.
Refs #21797 (the RFC's doc PR).
Checklist