Skins: no current scoreboard plugin builds on src.base_classes, so the only
skin hook (SportsCore._render_game) never runs. The plugin schema endpoint no
longer injects the Visual Skin dropdown, the store hides and refuses
"type": "skin" registry entries, and GET /api/v3/skins reports
supported: false with a message. Stored skin config still loads and saves.
src/skin_system/ and its tests are unchanged apart from the support flag.
Docs: check_plugin.py/render_plugin.py examples use --plugin; document
BasePlugin.get_update_interval() and its interaction with the manifest
update_interval; CLAUDE.md drops the stale template line number and
recommends display_manager.width/height.
Preview size: new src/display_geometry.py holds the size computation and
defaults DisplayManager uses (double-sided applied, chain_length default 2).
The web preview, /display/current, Starlark magnify default, sync handshake
and two dev scripts use it.
Release: __version__ 3.4.0, CHANGELOG 3.4.0 section plus a 3.3.0 tag note.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Add skin system: user-installable visual overlays for sports scoreboards
Skins restyle a scoreboard's live/recent/upcoming rendering while the
host plugin keeps doing data fetching, scheduling, caching, live
priority, and vegas mode — the anti-fork alternative for users who only
want a different layout.
- src/skin_system/: ScoreboardSkin API, SkinContext (canvas + adaptive
layout + logo/font helpers), discovery/loading runtime with API major
version gating and per-skin module namespacing
- src/base_classes/sports.py: _render_game() seam at the three
_draw_scorebug_layout call sites; skin-first with built-in fallback,
3-strikes session disable, slow-render warning; per-mode skin config
- scripts/validate_skin.py: headless multi-mode/multi-size validator
with bundled per-sport fixtures (no hardware or network needed)
- skins/example-classic-baseball/: working reference skin
- Web UI: served-schema Visual Skin dropdown (validation never
enum-restricted, so uninstalled skins can't invalidate configs) and
GET /api/v3/skins
- Store: registry entries with type "skin" install to skins/
- docs/SKIN_SYSTEM.md (architecture), docs/CREATING_SKINS.md (author
guide incl. Claude Code prompt), view-model contract locked by tests
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LrCusPasy1qeUN5anK3aA1
* Address review feedback on skin system
- skin_runtime: cache the entry module so the 2nd/3rd load of the same
skin (live/recent/upcoming hosts) doesn't re-execute it with unbound
sibling aliases; rebind cached sibling modules to their bare names
around entry import and restore prior bindings after; include per-
manifest mtimes in the discovery cache fingerprint so in-place skin
updates are picked up
- sports.py: count render_skin_card exceptions toward the 3-strike
session disable
- store_manager: validate skin ids (pattern + resolved-path containment
in skins/), reject registry/manifest id mismatches, and stage+validate
downloads in a temp sibling before replacing an existing skin
- schema_manager: leave the schema untouched when the configured skin
value is a per-mode mapping (a string dropdown could overwrite it)
- validate_skin.py: reject non-positive sizes and non-object --options
at parse time; support --output-dir outside the repo; type annotations
- example skin: validate accent_color once at load with logged fallback
- fixtures: pregame 0-0 scores in football/hockey upcoming fixtures
- api /skins: rely on the self-invalidating discovery cache instead of
force_refresh
- docs: valid JSON manifest example, load_logo caching semantics spelled
out, language ids on fenced blocks
- tests: view-model contract test now exercises the real extractor;
regression test for repeated same-skin loads with sibling modules
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LrCusPasy1qeUN5anK3aA1
---------
Co-authored-by: Claude <noreply@anthropic.com>
