Handoff

State of storebound for whoever picks it up next. Public-safe: no project, app or account names.

Released

npm, storebound.dev and the desktop app carry the latest tag (see CHANGELOG.md).
Releases: bun tools/release.ts <version> --yes runs everything in one command, npm included (docs/desktop-release.md).
- Background tests run on Forgejo and never gate a release. bun tools/ci-status.ts shows the newest result.
- The Linux and Windows updater signatures are made on the release server: bun tools/desktop-release.ts vds-key rotates its key, and --sign-local is the fallback.

Desktop report view + design v2 (paused by the owner).
- What it is: the readiness report inside the desktop app as its own screen, not only in the browser. Also a stronger design (a hero per store, "what to fix first", passed checks shown, a 1200x630 summary image).
- Where it is: half done, kept in a local git stash named "paused: report in desktop + design v2" (not pushed).
- How to resume: git stash list, then git stash apply, then finish the view and run the desktop typecheck and the fixture UI.
Two worktrees with uncommitted changes from other sessions:
- guardrail-2310-macos: Apple platform commands (iap-submit, release, resubmit, status);
- shots-bleed-landscape: landscape screenshots and uploads. Their owners decide; don't delete them without asking.
Not verified live yet:
- The IARC exact-label helper in the console plans (tested on a fake page only).
- The Play Games Services console page paths.
- The Games Configuration API bodies (no pinned spec).
- Placing a Header and Search Results asset on a live App Store version.
iPhone Duo: uploaded through the App Asset Library (cli/apple/duo-library.ts); previews still use the deprecated sets.

Every check, message and screen covers both stores and every surface (AGENTS.md, "Working on storebound itself").
Real projects reported most guardrails. They stay anonymous in the repo: neutral names and com.example.* only.