Skip to content

v1.14.0 — Studio settings and release hardening

Choose a tag to compare

@zdhoward zdhoward released this 28 Oct 15:46
· 37 commits to main since this release

v1.14.0 — Studio settings and release hardening

Scene Studio now has a dedicated service Settings tab, clearer generator headings, and hides sky controls that do not affect generator scenes. Settings saves preserve private configuration keys, validate values against the service's supported ranges, and replace the config atomically. Restart the service to apply settings; saving never flashes or restarts the display.

All Studio POST endpoints now require JSON and a loopback Host with matching origin/port. Request bodies are bounded and filesystem failures do not return private paths. Studio remains a local application, not a network-authenticated administration service.

This release also publishes the prior compact Console grid, direct Gemini quota source, cheap two-second quota reads, cached transcript aggregates, quota-transition history and configurable one-hour pre-reset wake. The owner reports the new wake behavior works well. Argon remains unknown until an independent measurement source is available; the owner's report that it is exhausted is not substituted for telemetry.

Verification and images

  • 49 service tests and 20 Studio tests passed. A Windows-incompatible epoch fixture was moved to a modern date without changing its age/countdown assertions.
  • Browser workflow passed: save/reload, dirty/revert/navigation prompts, generator sky controls hidden, image-scene sky controls visible, no JavaScript errors. Desktop and narrow layouts inspected.
  • JavaScript syntax and Python compilation passed. 21st review reported style/token suggestions; existing Studio appearance retained.
  • Screenshots in docs/img/: studio-settings.png, studio-generator.png, display-console.png, display-details.png, display-system.png, display-companion.png.
  • Display images are actual USB framebuffers captured from the running application. Studio Settings was captured with isolated public defaults; the Plasma scene is generated by project code. No personal image layers or credentials were published.

Remaining acceptance: portrait/Rows and six-account edge cases, logon startup, physical brightness transitions, optional Wi-Fi. Future screensavers, scene transitions, audio visualization and stock ticker remain on the backlog.