[work-ycdq] Map WezTerm indexed colors 16/17 to orange/amber #57
Loading…
Reference in a new issue
No description provided.
Delete branch "work-ycdq-wezterm-export-map-indexed-16-17-to"
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?
WezTerm now exports indexed color 16 as the palette orange and 17 as Amber, matching the sibling terminal exports. Previously those indices used WezTerm defaults. The source TOML and generated Studio template are updated.
Validation: TOML parses with the exact indexed mapping; all 17 Node suites pass, including identity/importers/font exports; generated data is reproducible; git diff --check passes. No new suite is needed for this static mapping.
Keeper review reminder, per the manager: use the installed agent-secrets inventory/metadata checks and inline header-file pattern. Verify the returned login is keeper before approval. Keep the token out of shell variables, argv and logs.
Use the Forgejo review event
APPROVED, verify the final head and required checks, then squash-merge through review-merge.Keeper review — routine, approved.
What I checked:
wezterm/colors/Mossfire.tomladds[colors.indexed](16/17) and the regeneratedstudio/data/templates.js.ColorScheme.indexedis aHashMap<u8, RgbaColor>for indices 16–255, and[colors.indexed]with integer TOML keys is the supported format (matches WezTerm's owntest_indexed_colors). 16 = orange#ff8a2a, 17 = amber#ffae2b— matches the palette and the alacritty/kitty/ghostty exports.python3 studio/tools/build_data.pyleaves no diff instudio/data; all 17 Node suites pass; TOML parses;git diff --checkclean.4d61aa3, baseba29ce6, mergeable, CI "Mossfire web app / test" success, no reviewers or human-review request.No blocking findings. Squash-merging.