* zgx: bump zgx to a264a40b (full screen to scripts, terminal colours)
Every zgx git dependency and the mirrored [patch.crates-io] entries move
from 99a50ad5 to a264a40b, zgx main's head, which holds both features
Zeron takes up next (`cargo update -p zgx`: only the zgx repo's own
crates' revisions change; zgx's patch set is the same seven crates):
- #1442: `ui.window.full_screen` and `ui.window.full_screen_transition`
(macOS's animation going in or out, and its duration), kept by
`ScriptHost::window_full_screen`.
- #1440 (4f8cc87b): a terminal's colours from the theme where it shows,
the `terminal.*` tokens, recoloured live.
zgx-asks/README.md records the new pin.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* zgx title bar: in macOS full screen the controls slide to where the traffic lights were
In full screen macOS hides the traffic lights, but the title bar's
controls (the sidebar's toggle, back, forward) stayed 88 in, leaving a
gap. They now take the window's edge inset there, 12, as Zeron's do
(crates/ui shell.rs `titlebar_cluster_start`), and slide back past the
lights as the window comes out.
- The host keeps `ui.window.full_screen` and its transition for every
window (setup, the intro, the main window): `ScriptHost::
window_full_screen` from `WindowInfo::fullscreen` and
`WindowContext::full_screen_transition` (zgx #1442). It also says the
platform (`platform`), and takes `window.full_screen` (a script's way
in and out, as the green button; the live check's fixture uses it).
- ds/title_bar: out of full screen the toggle stands 16 past the lights'
right edge (`ui.window.controls`: 12 in, 60 across, so 88 as before);
in full screen 12. Off macOS nothing changes (88, `window_buttons_right`
as it was). The island behind the controls, and a pane's title that
starts past them (the sidebar collapsed; a split's panes too), follow.
- How it moves: zgx draws no frames while macOS animates a window in or
out of full screen (its frames say "the window stopped presenting"
for the whole transition), so a slide timed to the system's animation
is never seen. The controls hold still through it, then slide over in
Zeron's 200 ms ease out once the window draws again (50 ms after the
transition ends: coming out, macOS reports the lights at 9,9 until a
moment after). The values are the engine's (`TitleBar.follow`): set or
animated by one call, nothing run per frame, nothing at rest.
tests/full_screen_titlebar.rs drives full screen and its transitions in
and out (the lights hidden, then at 9,9, then back, as measured) and
reads the toggle's box each frame: still through the transition, a
slide only left (then right) that lands on 12 (then 88), and no script
call while it slides; off macOS it never moves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* zgx themes: the terminal wears the theme's colours, legible in either scheme
Switching from a dark theme to a light one left the terminal unreadable,
pale text on white: its colours were the user's own Ghostty ones. zgx now
takes a terminal's colours from the theme (zgx #1440, the `terminal.*`
tokens, repainted live, scrollback kept); ds/palettes.tokens, the one
palette-to-tokens mapping, sets them for every theme, built in, a
template's or imported, light and dark, and for Zeron's own two (their
theme files otherwise stay as they are):
- the text the theme's (already legible), the cursor its accent with
black or white under it, the selection its accent mixed over the card
(Ghostty's colours are opaque, so no wash), the background the card
the pane shows over (the app draws the pane; Ghostty's own background
stays clear, so nothing turns opaque over glass);
- the sixteen ANSI colours held legible on the window's surfaces with
the inks' floor: 4.5:1, and 3:1 for the two that are the background's
own shade (black and bright black on dark, white and bright white on
light, so a light theme's pale white turns grey, never white on white).
What moved is said with the other inks' fixes, and
zeron_theme::catalog::legibility says the same (its parity test with
the window covers every built-in theme): 164 colours across the
built-in themes, most of them in light ones.
A scheme wearing Zeron's own takes these from Zeron's palette in the
host's list once it's there; a plugin lent the design system looks
nothing up.
src/themes.rs tests: every built-in theme's terminal text and sixteen
colours read at the floor on the window and on a menu, and Zeron's own
give a terminal shown in the window their colours, dark → light → dark,
the light text dark and the whites legible on white.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* zgx v2 template: the session title follows the controls in and out of full screen
Zeron v2 keeps its own copy of the shell's page; its session title,
past the title bar's controls with the sidebar collapsed, now moves
with them as the default's does: its `left` eases as the sidebar comes
and goes (out of full screen's place), and full screen's shift is its
`x`, kept by the title bar's `follow` (still while macOS animates, then
sliding with the controls). v2 recorded in step with the default
(ZERON_V2_BLESS).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* theme: one catalogue of themes for the window and the engine
zeron_theme::catalog holds what the window's Themes page and an agent's
theme tools both need: the built-in, template and imported themes, the
palette shape ds/palettes wears (read with every problem said, written
back the same), themes made from palettes, update and delete for yours,
the light and dark choice, and which inks the window moves to keep a
palette legible (checked against the window's own mapping in zgx's
tests). zeron_theme::luau_data reads a template's theme.luau as data.
The zgx app's themes host now uses it, and reads the files again when
the engine says its tools changed them (WatchThemes).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* engine, mcp: theme tools for agents
list_themes, get_theme, create_theme, update_theme, delete_theme and
use_theme, over the engine's ListThemes … UseTheme on this device's
theme files. A theme is data, so nothing asks the person; only yours
can be changed or deleted, a built-in or template theme is copied
instead. Palettes are checked with clear errors, a VS Code theme's JSON
comes in through the importer, and each reply says which colours the
window wears lighter or darker to stay legible.
The methods are local-only (a peer never reads or writes another
device's themes) and open to the agent token, but not the window's
WatchThemes. docs/themes.md is served to agents as the other guides are.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* zgx: a theme changed outside the window restyles it; docs for the tools
The Themes fixture can change the library as an agent's tools would,
and a test checks the page lists the new theme and the theme in use
restyles. README and templates.md point to the theme tools.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>