0.24.4
The operator UI is the release. Its connections page is now a summary line and
one row per connector instead of a wall of expanded cards, and the stylesheet
behind it resolves through design tokens a deployment can set with the new
branding.theme. Nothing a deployment configures today changes meaning, no
storage format moved, and the page shows exactly what it showed before under
the same gates — an operator who has the page bookmarked will find it reads
differently, and that is the whole of the upgrade. The documentation cut to
four guides lands here too, along with one execution-path fix.
Added
branding.theme. Five tokens —accent,radius,fontFamily,
monoFamily, andcolorScheme— set onoperatorUi({ branding }). Every
other color on the operator page is mixed from those. Light and dark are the
same tokens and follow the operator's OS setting unlesscolorSchemepins
one. Each token is gated: a hex color, a CSS length, a plain font-family
list, one ofsystem/light/dark. A rejected value takes the default and
gets named in a startup warning (#554).
Changed
- The operator UI reads as a dashboard. One summary line, then one row per
connector; the description, permission line, OAuth actions, credential panel,
diagnostics, drift, and tool list are behind a row an operator expands. Same
payload, same gates (#554). - The documentation is four guides.
architecture.md,meta-tools.md,
code-mode.md, andauth.md; each release's changelog paragraph is the
upgrade guidance (#552, #553).
Fixed
get_resultpaging cost. A page reads and decodes only the chunks it
covers rather than the whole stash. Offsets,nextOffset,totalBytes, and
character-boundary alignment are unchanged, and entries stashed in the
previous formats stay readable for the rest of their 15-minute TTL (#540).
Full changelog: https://github.com/zackbart/connecta/blob/v0.24.4/CHANGELOG.md