prep-major-release

Prepare Glassbox for a major release. A lot has usually changed since the last release, so the public-facing story drifts: the **README** stops advertising the best features, and the **demo screenshots** stop matching the UI. This skill brings both back in line. Two deliverables, in order: 1. **README.md** — reviewed and updated so it stays compelling and advertises the most important and interesting features. 2. **Demo scenarios + screenshot scenes** — reviewed, with any *new / different / fewer* screenshots proposed and the **code changes applied**, then handed off to the maintainer to capture. **Do not capture screenshots yourself** — capturing needs Chromium outside the command sandbox and the maintainer does it (they said so). Your job is to get the scenes *ready to capture* and tell them exactly what to run. ## Step 0 — Orient (what's new since last time) Before touching the README, build an accurate picture of the current feature set so you advertise what actually ships today, not what shipped a year ago: - Read `docs/ai/requirements-summary.md` and `docs/ai/code-summary.md` — the fastest synthesis of every feature and its status (Shipped / Partial / …). - Skim the requirements index in `CLAUDE.md` and any newer numbered docs in `docs/` that the README predates. - `git log --oneline -40` (or since the last release tag: `git log --oneline $(git describe --tags --abbrev=0 2>/dev/null)..HEAD`) to see what landed. - Note features that are **shi...