Skip to content

Covel v0.0.22

Choose a tag to compare

@github-actions github-actions released this 26 Jul 05:33
· 2505 commits to main since this release

[0.0.22] - 2026-07-26

Appearance stops being a three-way switch. The token system was already complete — every theme defines it and every atom consumes it — so what was missing was never the plumbing, only a way for the player to reach it. This release exposes 45 of those tokens grouped by the region they affect, adds a path from "I tuned it" to "here is a theme package", and publishes turn state to the DOM so a theme can finally react to what the game is doing. The rest is player-facing correctness: two inputs that accepted what they shouldn't, and one that rendered less than it should.

Added

  • Settings → Appearance: 45 adjustable design tokens. The panel previously offered a theme picker, a light/dark toggle, and a CSS file import — anything finer meant hand-writing a theme. Tokens are now grouped the way a player thinks about the screen (narrative type, interface type, region backgrounds, text and rules, accents, ambience, shape, layout sizes) rather than by variable name, and the whole surface is driven by one declaration table (token-schema.ts) — adding a knob is a row, not a pipeline. Overrides apply as inline styles on <html>, which outrank any stylesheet, so clearing one restores the theme's value exactly rather than recomputing it. Colours are stored per scheme and sizes/fonts shared: the same colour is rarely right in both light and dark, but "I want bigger text" is not a per-scheme preference. Dragging a slider paints straight to the DOM and only the settled value reaches storage — persisting every frame would write localStorage 60×/second. The font list includes CJK serif/kai/hei stacks, which is what makes long-form Chinese prose readable and is not available from a generic system stack.
  • Save the current look as a theme package. Closes the gap between the panel and hand-written CSS: bake the active theme plus every override into a standalone package, then export it, share it, or open it and add effects by hand. The snapshot covers the whole token contract rather than only the overridden tokens — a package carrying just the changes would fall back to base values everywhere else, so "save what I see" would visibly change what you see. Theme ids stay off the builtin namespace (a custom theme claiming a builtin id is dropped on the next registry sync, so saving one would appear to work and then vanish), a single-scheme source stays single-scheme, and generated declarations drop any value containing ; or braces, since that CSS is re-parsed as a theme and such a value can close the rule early and escape its scope.
  • Turn state is published to the DOM for themes to hook. <html> now carries data-turn (idle / executing / waiting / error) and data-session, so a theme can style what the game is doing — an input that breathes while the model writes, an alarm pulse on failure — which pure CSS previously had no way to ask about. waiting outranks executing: the turn is still open but the kernel is blocked on the player, and that is the state worth highlighting. Deliberately framework-owned and coarse; plugin-specific state (scene, mood, combat) needs a declared capability channel rather than hardcoded plugin ids, and is not part of this.
  • aurora, a reference theme for effects. Glassmorphism, an @property-driven drifting gradient, message entrance animation, hover glow, and the turn-state effects above — as a builtin the player can just pick, and as the thing to copy when writing one. It passes the same import validation a player's theme goes through, so copying it cannot land you outside the scope rules; a test holds that.
  • The studio rail starts collapsed and remembers its layout. The left rail holds studio configuration — plugin toggles, model slots — none of which a player acts on while reading, yet it opened at 20% every session and left the narrative column about 40% of a 1440px viewport. Collapsed it gets 69%, and whatever the player does next survives a reload, stored through useDefaultLayout rather than hand-rolled localStorage. Mobile and desktop keep separate entries, since the mobile group stacks vertically and puts the right rail in a different slot.

Fixed

  • Player messages render as markdown. They went through a bare <p>, so markdown syntax showed as literal characters and real newlines collapsed into spaces — choice text carrying its own line structure arrived as one flat paragraph. They now use the same renderer as the narrative, with lone newlines promoted to markdown hard breaks first (markdown otherwise folds a single newline into a space, so the player's Enter key silently did nothing). A literal backslash-n is deliberately left alone: that is over-escaped model output rather than a break, and rewriting it in the view layer would hide a data bug and misrender any text discussing \n.
  • The composer is locked until the adventure begins. The "begin adventure" hero renders on messages.length === 0 && !executing && isPreGame, but the composer only disabled itself for an unanswered interaction block — two unrelated conditions, so the button sat waiting to be clicked while the input stayed live. Sending from there opened a turn before any setup runtime had run, leaving the narrator to answer in a world with no character and no opening scene. Folding the condition into composerDisabled covers the Enter key too, since handleSubmit already guards on it. Kept out of composerBlocked, which means "an interaction is unanswered", drives its own placeholder, and is what e2e reads via data-blocked. The pre-game predicate now lives in one place shared by the hero and the composer — two copies of the same rule drifting apart is exactly how the gap appeared.
  • Author-facing detail stays out of the player view. Every message header carried its full 36-character turn UUID, meaningless to a player and a whole line on a phone, while every other author-facing detail in the same file was already gated on viewMode. It now follows the same rule. The stage dialog box is clickable to advance or skip the typewriter but had only cursor: pointer behind it — no hover state, and no accessible name, so a screen reader announced an empty button.

Changed

  • CI stops invalidating its own test cache. test listed plugins/** as an input, which pulled each plugin's run artefacts — vitest's results.json, turbo's turbo-test.log — into the hash. Running the suite rewrote those files, so the next run hashed differently and all 43 packages missed; running tests was what invalidated the test cache, and it never settled above 2/43. Explicit input globs do not consult gitignore. The build step also moves behind push (scoped to main): it covers the bundling layer that tsc --noEmit cannot see, which is worth keeping but not ~2 minutes on every PR push.

What's Changed

  • ci: stop the test cache self-invalidating, and drop duplicate PR runs by @ackness in #30
  • ci: run the build step on main only, not on every PR by @ackness in #31
  • Release v0.0.22 by @ackness in #32

Full Changelog: v0.0.21...v0.0.22