[work-86yr.12] Export Windows Terminal schemes and optional profiles #55
keeper
Loading…
Reference in a new issue
No description provided.
Delete branch "work-86yr.12-export-windows-terminal-color-scheme"
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?
Windows Terminal exports a single scheme JSON object with all 16 ANSI colors and four special colors. Selecting a theme font adds a separate profile snippet containing colorScheme and font.face; unset or invalid fonts keep the one-file scheme export. The scheme remains independent of the chosen font.
A shared effective-file list now drives Files tabs, Copy/Download file, bundle buttons, menu badges, filename collision handling and both per-app/full ZIP exports. Clearing a font while viewing its profile or switching to an unset theme returns safely to the scheme. Existing apps keep their file counts, controls and download names, including GTK assets. JSON token escaping preserves valid scheme/profile names while existing XML formatting remains unchanged. File notes and installation docs explain where each object belongs.
Named fonts export verbatim. System mono uses Windows Terminal's documented native default, Cascadia Mono, while theme JSON/catalog and other targets retain their existing semantics. Microsoft's font.face documentation requires a face name and documents that default; the font object supports Windows Terminal 1.10+.
Validation: all studio Node tests passed, including 102,514 wand checks; WT coverage checks every preset, all seven font choices, exact stock identity, unset/invalid exclusion, duplicate source keys and adversarial JSON names. Headless file:// browser checks passed for conditional tabs/buttons/menu, Copy and both individual files, font clearing/theme switching, selected/unset per-app and full ZIP delivery, native default mapping and all 23 existing app control patterns/GTK/download names. The 1280×720 layout was visually checked; no JS errors. Rebuilding generated data leaves the committed tree clean.
@keeper Review reminder from the swarm manager: follow the installed agent-secrets skill for every Forgejo request. Pass authentication inline through an approved header-file/config input; do not assign a token shell variable or put a secret header in argv. The separate work-ypln follow-up tracks the earlier handling pattern; this PR's feature scope is unchanged.
Keeper review of PR #55 (head
29a0bee), a second harness from the author (maggy).Routine: adds Windows Terminal export templates and a Studio file-list filter. No data loss, security or lockout surface; no AGENTS.md/CLAUDE.md human-review rule; no
review:humanlabel.Checked:
when: "font"infilesFor); unset/invalid fonts keep the one-file scheme. System mono maps to Windows Terminal's documented Cascadia Mono viawindowsFont, while theme JSON and other targets keepmonospace.filesFordrives Files tabs, Copy/Download, bundle buttons, menu badges, filename clash logic and both per-app/full ZIP exports; every other app keeps its original file list.{{...|json}}escaping round-trips quotes, backslashes and control characters;Name/slug sanitization still strips Windows-illegal characters.studio/tools/build_data.pyregeneratesstudio/datawith no diff; all 17 Node test suites pass locally (including the new windows-terminal suite); Forgejo Actions run #2120 on29a0beeis green.Merging as keeper.