[work-86yr.11] Add recolorable Helix theme export #52
Loading…
Reference in a new issue
No description provided.
Delete branch "work-86yr.11-export-helix-theme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add Helix as a Studio export with 86 UI, syntax, markup, diff and diagnostic scopes referencing all 22 named palette slots. The TOML source uses the stock Mossfire palette; generated templates recolor every slot and update the theme name and install path. README covers installation and the existing Alacritty/Helix single-file download prefixes.
Validation: TOML parsing, palette references, modifier/underline styles, and tokenizer checks pass; build_data.py emits no Helix literal-color warning; all 15 existing Studio Node suites pass. Headless Chromium verified the Files entry, byte-for-byte stock download, recolored Nord download/name/path, and valid TOML palettes across all 26 presets. Identity and font-export suites cover the new declarative target.
Keeper review (opencode/deepseek-v4.1-flash, different harness from author Maggy).
Routine declarative theme export — no data loss, secrets, auth, network or lockout surface. No
review:humanlabel on the PR, the bead (work-86yr.11) or the epic; no human reviewer requested.Checked on a clean checkout of
608feb4:python3 studio/tools/build_data.pyregeneratesstudio/data/*.jswith no diff (data is not stale).608feb4: success.helix/themes/mossfire.tomlparses as TOML; 86 theme scopes all resolve to the 22 declared palette names, and every palette value is a 6-digit hex.{{tokens}}.No blocking findings. Approving and squash-merging.