Commit 4 BINDING design specs into docs/proposals/mockups/ for durability - #441
Merged
Merged
Conversation
rail-delegacy, editor-polish, cardback-pdfwait, wtc-rebuild — each cited by filename in committed code comments (the first three now on master via PR #431) but previously living only in a session tmp dir that dies with the session. Verbatim copies + companion mockup HTML, same durability convention as reference/funnel-spec.md.
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A durability gap: four BINDING, owner-approved design specs (
rail-delegacy,editor-polish,cardback-pdfwait,wtc-rebuild) lived only in a session's tmp dir — which does not survive past that session — while committed code comments across the repo already cite each spec by filename as its authority. Same failure modedocs/reference/funnel-spec.mdwas recovered from during the 2026-07-23 D-lettering sweep. This PR brings all four into the repo, following thedocs/proposals/mockups/proposal-h/precedent (spec + companion static-HTML mockup, one directory per round).What shipped
docs/proposals/mockups/{rail-delegacy,editor-polish,cardback-pdfwait,wtc-rebuild}/SPEC-*.md+ each spec's companion mockup HTML (*-mockup.html), copied verbatim (including OWNER AMENDMENTS sections where present —editor-polishandcardback-pdfwaithave one,rail-delegacy/wtc-rebuilddon't).wtc-rebuild's header notes this explicitly since its own line 4 mentions "+ PNGs (this dir)".SPEC-*.md(the only content edit beyond mechanical formatting): origin date (2026-07-24), which committed files cite it by filename, and a pointer tofunnel-spec.mdas the precedent for this durability convention.docs/proposals/mockups/README.md(new) indexes all five bundles (proposal-h/+ the four new ones) and explains why the four are here.docs/README.md's Records section links the new index, so the bundle is reachable from the index chain (thoughproposals/mockups/is already exempt from the orphan check as an archive-prefix bucket).Mechanical fixes only, content otherwise verbatim
npx prettier@2.7.1 --writeon eachSPEC-*.md(repo convention / pre-commit hook scope). Verified per-file: idempotent on a second pass, and diffed against the tmp originals — the only changes are table-column realignment, wrapped-prose reflow, and safe*text*→_text_/bare-*→\*emphasis-marker normalization (the corruption failure mode indocs/lessons.md's prettier entry — intraword-underscore breakage — does not appear anywhere in these files; none use bare underscores in prose)./whatsthat/#.Durability rationale / code-comment citation check
Per the task's ask, grepped committed code (
frontend/src,MPCAutofill) for both the spec filenames and the literal tmp path:SPEC-rail-delegacy.md,SPEC-editor-polish.md,SPEC-cardback-pdfwait.mdare now cited by ~40 committed files onmasteritself (landed via Cardback reminder gate + apply-all/set-default prompts + PDF-wait experience #431, which merged ontomasterduring this PR's session — this branch is rebased past it) — e.g.DisplayPage.tsx,SelectVersionResults.tsx,PDFGenerator.tsx,AutofillCollapse.tsx,SourcesAccordion.tsx,RequestedPrintingBadge.tsx,PrePrintSaveGate.tsx,CommonCardback.tsx, plus their test/spec files.SPEC-wtc-rebuild.mdis cited on the still-open PR Re-theme site to Tokyo-11 (Tokyo Night, orange action, purple accent, Semi radius) #438 (tokyo-11-retheme) branch —ChipCard.tsx,WhatsThatWords.tsx,cardPanel.tsx— not yet onmaster./home/ubuntu/.claude/jobs/...) — every citation uses the bareSPEC-*.mdfilename, which is exactly why bringing the specs into the repo under their original filenames resolves the citations with no code changes needed. No follow-up path-fix items to flag.Verification
python3 .github/scripts/docs_lint.py --strict: clean (0 hard findings, 0 soft findings).python3 .github/scripts/tests/test_docs_lint.py: 26/26 pass (includes the real-repo full-corpus check).python3 .github/scripts/tests/test_publish_wiki_link_rewrite.py: 4/4 pass.python3 .github/scripts/tests/test_publish_readme.py+publish_readme.pyregenerate-and-diff: pass, zero drift (this PR doesn't touchreadme.md's source regions).npx prettier@2.7.1 --checkon every changed/added markdown file: clean.docs/proposals/is excluded from the wiki publish map), so the Policy-text and Wiki-maintenance checklist items don't apply.Checklist
pre-commitand installed the hooks withpre-commit installbefore creating any commits.docs_lint.py --strict, the docs-lint/link-rewrite/readme-parity test suites, andprettier --checkon every changed file (see Verification).