Rebuild the editor as a Vue app: sidebar, pages side by side, tile settings in a drawer (0.2.74)

The page is now web/ (Vue 3 + Vite + TypeScript), built into screen_manager/app/static
with hashed file names; server.py serves index.html as built and /assets/. The Python
API, the data and the firmware are unchanged. Your screens sit in a sidebar, the pages
of a screen stand next to each other at the screen's own shape, the library sits on the
right, and a tile's settings slide in as a drawer while the mockup stays in view. New
screen, Firmware & USB, Alerts, Override YAML and Settings are pages of their own.
Fonts moved to web/src/assets; the tests read the source through tests/editor_sources.py.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

AGENTS.md

@@ -54,6 +54,10 @@ and screens for lookups and tests. If that file is missing you are not on his ma
 
 - Keep base hardware and UI in `home-like-2432s028.yaml`; personal data belongs
   in the gitignored local profiles.
+- The editor is `web/` (Vue 3 + Vite, TypeScript; app 0.2.74+). `screen_manager/app/static` is its build
+  output: change `web/src`, run `cd web && npm run build`, and commit both. Keep every URL the page asks for
+  relative (`api/...`), so it works behind Home Assistant's ingress path. Tests read the source through
+  `tests/editor_sources.py`; docs/RELEASING.md "Local development" has the dev-server recipe.
 - Colours live in one table: `components/smart_display/theme.h` (firmware 0.2.54+). Every role has a
   light and a dark value, board profiles name paints (`styles: paint_card`) instead of writing a colour,
   and firmware code asks for a role (`theme::color(theme::INK)`). Never write a hex colour in a profile or