feat(standard): §11.3.5 Tokyo Night, §11.5 fidelity palettes, §11.4.1 reference names — v1.39 - #18
Conversation
… reference names — v1.39 Registers three external palettes and adds the class the two of them that cannot conform belong in. §11.3.5 — Tokyo Night, verbatim from enkia/tokyo-night-vscode-theme: canvas Night #1A1B26, surface the documented Storm background #24283B, surface-alt the Night bg_dark #16161E (darker than the canvas, which §11.0.1 permits). No Spacecraft-derived substitutes were needed — every role token clears 4.5:1 on all three backgrounds — so it is registered as a conforming alternate. tokyonight-high-contrast lifts the two tokens under 7:1 on the canvas (accent #97B6F9, error #F998AA). The upstream comment tone #565F89 (2.76:1) is recorded as unbindable. §11.5 — Fidelity Palettes (registered, non-conforming). Solarized Dark and Solarized Light are reproduced exactly from ethanschoonover.com with no token substituted, deepened, or lifted, and they do not satisfy §11's contrast guarantee: Solarized Light's body text is 4.13:1, under the AA floor, and its success/warning/focus tokens fall below 3:1. The printed ratios are the measurement, not a target. §11.5 bars adopting a fidelity palette as a project palette, keeps steelbore-mono as the accessible path, and ships no high-contrast sibling for them. §11.4.1 — Reference Names. Every palette gains an additive reference name for prose (steelbore-color-palette, steelboreclassic-color-palette, blue-, blackpinkpanther-, matrixgreen-, navywhite-, tokyonight-, solarizeddark-, solarizedlight-color-palette). Slugs are unchanged and remain the machine identifier, so no consumer breaks. Every ratio in §11.3.5, §11.5, and the changelog was computed from the canonical steelbore.toml rather than transcribed, then re-verified against it. Verified: makeinfo --no-split → zero errors/warnings; reuse lint → compliant 8/8; .md companion regenerated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
![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: 5d071e2386
ℹ️ 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".
| Anchored on @strong{Night} and @strong{Tokyo Blue}, registered verbatim | ||
| from the upstream editor theme (@uref{https://github.com/enkia/tokyo-night-vscode-theme,enkia/tokyo-night-vscode-theme}). | ||
| @code{surface} is that project's documented @emph{Storm} background and | ||
| @code{surface-alt} its @emph{Night} @code{bg_dark} --- like MatrixGreen's |
There was a problem hiding this comment.
The cited Enkia VS Code theme does not define the palette described here: its documented Night palette uses #A9B1D6 for foreground, #AD8EE6 for magenta, and #444B6A for comments, whereas fg = #C0CAF5, magenta = #BB9AF7, comment = #565F89, and the bg_dark identifier come from folke/tokyonight.nvim. Consequently, the new palette is not reproduced verbatim from the linked upstream, which gives consumers incorrect provenance; either cite the Neovim theme or change the values to Enkia's palette.
Useful? React with 👍 / 👎.
| Where an application offers one as a @emph{user-selectable} theme, a | ||
| conforming palette remains the default, and @code{steelbore-mono} (§11.1.1, | ||
| palette-independent) remains the accessible-mode path. |
There was a problem hiding this comment.
When a user selects either fidelity theme, the application immediately violates the supposedly unaffected §13 requirement that every color pairing meet WCAG AA—for example, Solarized Light body text is only 4.13:1 on the canvas and 3.64:1 on its surface. Keeping a conforming default or offering steelbore-mono does not make the currently selected UI compliant, so the standard simultaneously permits and forbids the same application behavior; define an explicit opt-in §13 exception or limit fidelity palettes to exported configurations rather than application themes.
Useful? React with 👍 / 👎.
…ames — v1.39 (#19) Back-sync of Spacecraft-Software/Standard#18, plus the canonical data. assets/steelbore.toml -> v3.1.0: 9 palettes, 17 themes. - tokyonight + tokyonight-high-contrast (§11.3.5), verbatim from the upstream editor theme; every role token clears 4.5:1 on all three backgrounds, so no Spacecraft-derived substitutes were needed. - solarized-dark + solarized-light (§11.5 fidelity palettes), reproduced exactly from ethanschoonover.com and carrying conformance = "non-conforming" plus an explicit below-3-to-1 list. Solarized defines one elevated tone per mode, so surface-alt shares surface. No high-contrast siblings: lifting would change the values they exist to reproduce. - reference = "<name>-color-palette" added to all nine palettes (§11.4.1). Slugs are unchanged, so no consumer breaks. - meta.fidelity-palettes added. spacecraft-standard-constitution/SKILL.md: §11.3 table + §11.3.5, §11.4 bullets, §11.4.1 reference-name table, §11.5 fidelity palettes; masthead and frontmatter to v1.39 (description 955 chars). steelbore-color-palette/SKILL.md: family table extended to nine, the fidelity carve-out and reference names documented, TOML row updated to 17 themes; frontmatter description rewritten to 966 chars — the edit had pushed it to 1059, over the 1024-character load limit. Every contrast value was computed from the palette hexes, not transcribed: 234 published ratios across 17 themes re-derived, zero mismatches. Both skills' bundles rebuilt in the same commit. reuse lint: compliant. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 participant
Registers Tokyo Night, Solarized Dark, and Solarized Light — and adds the class the last two belong in.
§11.3.5 — Tokyo Night (conforming alternate)
Verbatim from enkia/tokyo-night-vscode-theme. Canvas Night
#1A1B26,surfacethe documented Storm background#24283B,surface-altthe Nightbg_dark#16161E— darker than the canvas, which §11.0.1 already permits (MatrixGreen does the same).It needed no concessions. Every role token clears 4.5:1 on all three backgrounds:
#C0CAF5#7AA2F7#BB9AF7#9ECE6A#F7768E#E0AF68#7DCFFFtokyonight-high-contrastlifts the two under 7:1 (accent→#97B6F98.44:1,error→#F998AA8.22:1). The upstream comment tone#565F89(2.76:1) is recorded as not bindable to a role token.§11.5 — Fidelity Palettes (registered, non-conforming)
A new class for palettes reproduced exactly from a widely used external theme, so tooling can meet a user already working in it. Registered per your call to keep them verbatim and flag them honestly.
Solarized Dark — body text
base04.75:1 on the canvas; twelve pairings below 4.5:1;structure/border(2.97:1) anderror(2.81:1) below 3:1 onbase02.Solarized Light — body text
base00measures 4.13:1, under the AA floor, andsuccess(2.97:1),warning(2.98:1),focus(2.93:1) fall below 3:1. An interface built on it cannot signal status by color at all.§11.5 therefore: bars adopting a fidelity palette as a project's §11.4 palette, keeps
steelbore-monoas the accessible-mode path, ships no-high-contrastsibling (lifting would change the values they exist to reproduce), and marks the two failure bands † (3:1–4.5:1) and ‡ (below 3:1). Solarized defines one elevated tone per mode, sosurface-altsharessurface.§11.4.1 — Reference Names
Additive, non-breaking: slugs stay the machine identifier, reference names are for prose.
steelbore-color-palette·steelboreclassic-color-palette·blue-color-palette·blackpinkpanther-color-palette·matrixgreen-color-palette·navywhite-color-palette·tokyonight-color-palette·solarizeddark-color-palette·solarizedlight-color-paletteVerification
steelbore.toml, not transcribed — then re-verified against it (234 published ratios across 17 themes, zero mismatches)makeinfo --no-split→ zero errors, zero warningsreuse lint→ compliant, 8/8Construct sync (
steelbore.toml,SKILL.md,references/CHANGELOG.md, bundles) lands as its own PR at the same version.🤖 Generated with Claude Code