pre-deploylisted

# pre-deploy Run the full local verify and confirm the site is safe to push to Vercel. ## When invoked Use this skill when asked to check if changes are ready to push, deploy, or ship — phrases like "is this ready to push?", "run the build", "pre-deploy check", "check before I push". ## Instructions 1. **Run the full verify** from the repo root: ``` npm run verify ``` This is the single source of truth for local checks and mirrors the CI jobs in `.github/workflows/ci.yml`, minus the three CI-only checks CLAUDE.md's **CI & Local Verify** section records as deliberate exceptions (Chromatic, the dependency audit, the drift guard) — so a green verify can still meet a red CI on news from outside, like a fresh advisory. It runs, in order: ESLint, the library type-check, the publishable package build (`build:lib` — vite lib mode + d.ts into `dist/`), the story tests (every Storybook story rendered in headless Chromium, **with axe asserting WCAG 2.1 AA on each one** — an accessibility violation fails the suite exactly like a render error), the Storybook build, the website lint, the website build, and then the checks that need the finished build rather than source: `validate-rendered-spacing.mjs` (a space lost between JSX and render), `validate-corpus-coverage.mjs` (page prose that never reached the chat corpus) and `validate-internal-links.mjs` (an href pointing at a route that no longer exists) read the prerendered HTML, while `smoke-hydration.mjs` and `validate-web