every helix and zed theme on the machine, not a curated nine

228 in the ring: 3 pardes ships plus all 214 helix runtime themes and all 11
zed variants across its three families. No exclusions.

inherits is what this cost. 76 themes need it, so the reader is two passes now,
and the merge is WHOLE-KEY rather than field-wise because helix merges the
theme body at depth 1 — the three *_transparent themes clear their parent's
background with an empty table, and a field-wise merge would leave it painted.
I had that wrong until I read helix-view/src/theme.rs.

At 214 files the generator meets themes that are SPARSE rather than broken, and
the old fatal-on-anything-missing would have rejected them. Every fallback is
helix's own rule: no background at all means wear the terminal's, so bg and fg
go null (13 themes, correctly); the twelve RGB fields that cannot be null fall
back to ghostty's default palette entries 7 and 0, which is exactly what a
pardes terminal already paints an unstyled ANSI index as. fatal is kept for
what genuinely cannot be read.

Three real bugs surfaced only at scale: #ccc shorthand doubles the nibble
(helix's rule, 58 colours), a quoted inline-table key silently dropped a
selection colour, and four themes name a cursor background EQUAL to the page
because they are about to reverse that cell — taking it painted an invisible
move box. 0 degenerate themes out of 225 now: no fg==bg, no syntax colour on
its own background, no invisible box.

Collisions get an unconditional rule rather than a clever one: a zed variant is
always <name>_zed, because both projects ship gruvbox, ayu and one, and a
conditional tag would move a name when the other source changes. A comptime
assert holds it.

Cost: no-op build 0.257 -> 0.276s, a pardes.zig change 46.8 -> 47.5s, binary
+0.98%. The generator does 217 sources in 54ms.

NextColor stays and is no longer a way to REACH a theme — but the browse got
better, not worse: the generated half sorts by name, so its neighbours are that
theme's own family. theme.golden's fourth click moved from ayu_dark to acid,
which sorting 225 names does; themesel gained a tail capture proving row 228
renders.

1 files changed, 5 insertions, 3 deletions

diff --git a/docs/design.typ b/docs/design.typ
index 5d6daad2..763dcde4 100644
--- a/docs/design.typ
+++ b/docs/design.typ
@@ -96,7 +96,7 @@ Pardes
   panes:     []Pane         // slot array; id = index
   active:    Pane.Id
   drag:      Drag           // none | select | move | border | scrollbar
-  theme:     u2             // index into themes
+  theme:     usize          // index into themes (228 of them)
   colors_on: bool
   surface:   Surface        // rebuilt by surface(), arena-backed
   effects:   Fifo(Effect)
@@ -247,11 +247,13 @@ palettes, ascii glyph set toggle). Tutor: embedded text as file pane.
 first — helix (default; near-black page, chrome one grey-ramp step off it,
 colors lifted from the helix editor's own theme), dark, acme-light — then
 everything `tools/gen_themes.zig` exports at build time out of the vendored
-helix `.toml` and zed `.json` sources in `vendor/themes`. helix and dark leave
+helix `.toml` and zed `.json` sources in `vendor/themes`, which is all 214 helix
+ships plus zed's 11, sorted by name. helix and dark leave
 a child's ANSI palette native; acme-light and the zed exports resolve it onto
 the page so shell output stays readable on a light one. A theme owns the page,
 the tag bar, the gutter and the move box; the selection colors stay fixed
-because they encode which button you pressed. `NextColor` walks the ring,
+because they encode which button you pressed. `NextColor` browses the ring one
+step at a time — at 228 it is no longer how you REACH one —
 `Theme <name>` jumps to one and `ThemeSel` (`SPC t t`) lists them all into an
 output buffer whose rows are those very commands — so n/N EXECUTE each row
 instead of looking it and stepping the list wears the themes. Colors toggles