sync-changeslisted

# Sync and deliver changes This is a template: `main` is *not* guaranteed to be any given adopter's production branch — that's a per-project decision, not something this repo declares. On many projects it will be (this repo's own README documents `VERCEL_ENV` disambiguating a production deploy from a preview one, which only matters if `main` is what ships to production), but treat that as unconfirmed until you know otherwise. **Before your first commit in a session, confirm which branch this project actually deploys from** — ask the operator, or check the hosting provider's project settings (e.g. Vercel's Production Branch) — and treat *that* branch, not necessarily `main`, as the one nothing gets pushed to directly. If you cannot confirm it, assume the worst case (that the branch you're on ships live) rather than the permissive one. Committing directly to the live branch publishes to whoever is looking at the live site, with nobody having reviewed it first. This repo's own CI (`.github/workflows/ci.yml`) runs `pnpm run checks` on every pull request — the same command you run locally, covering `harness:check`, `content:check`, `catalog:check`, `gallery:check`, `lint`, `test`, `typecheck`, and `build`. That gate only fires on a PR, so a direct push to any branch that skips the PR step skips it entirely. Run `pnpm run checks` before you deliver: CI runs the identical script, so a failure there is one you could have seen first. ## The workflow 1. **Pull before editing, and sa