chore: add minimal validation — format, typecheck, CI

[jigarkhwar]

What changed

Minimal validation for the site: formatting, type checking / compilation, and CI that enforces both on every PR.

Two tools, four devDependencies:

• Format — Prettier + prettier-plugin-astro, config matching the code style already in the repo (single quotes, semicolons, printWidth 100).
• Typecheck / compilation — @astrojs/check + typescript, as npm run typecheck. astro build alone does not typecheck — it strips TS via esbuild, so a bad product tag or malformed code token compiles fine and only shows up as a broken card in the browser. astro check rejects it at the source (verified: swapping one product's tag to an invalid value fails the check with Type '"Bogus"' is not assignable to type '"Plugin" | "AI" | ...').
• CI (.github/workflows/ci.yml) — pull_request + push to main: checkout, Node 22 (Astro 7 needs >=22.12.0, now pinned via engines), npm ci, then format:check / typecheck / build as separate steps so a red PR names the check that broke. Nothing gated a PR before this — deploy.yml only builds and deploys on push to main, so a change that failed to typecheck would land and then break the deploy.

npm run validate chains all three locally.

Deliberately left out

An earlier revision of this PR also added ESLint and Vitest. Both are dropped to keep the dependency footprint small — measured, not guessed:

	npm packages added over main
prettier + prettier-plugin-astro + typescript	+7
@astrojs/check	+74
eslint + eslint-plugin-astro + typescript-eslint + vitest	+136 ← dropped

• ESLint — 3 packages plus a config to police ~30 lines of inline DOM wiring. astro check already covers the type-level errors that actually break this site. Easy to add later if the JS surface grows.
• Vitest — the tests worth writing here (product has a recognized tag, code tokens use a known syntax class, required fields present) are the same invariants Product / CodeToken already encode as types and astro check already enforces. Runtime assertions restating the type system are upkeep without coverage.

@astrojs/check is the expensive one at 74 packages, but it's what the official npm create astro scaffold ships for TypeScript projects, it's devDependencies-only (zero effect on the shipped site), and it's what makes the deleted tests unnecessary. Say the word if you'd rather drop it too and rely on astro build alone — that would take this to +7 packages, at the cost of no type checking at all.

Commits

1. Tooling — configs, 4 devDependencies, and a // prettier-ignore above each product's code: array in site.ts (each array packs several token tuples per line so the line mirrors the source line it renders as; prettier's default array-breaking would expand each snippet to 20+ lines).
2. Formatting — mechanical npm run format over the site source, plus a two-line var → const in BaseLayout's pre-paint theme script. README.md and profile/ are in .prettierignore — org-facing content, not site source, and reflowing their markdown tables would be churn in files this change has no reason to touch.
3. CI — the workflow.

Verification

npm run validate green end to end; lockfile confirmed in sync with package.json and free of the removed tools (CI installs with npm ci). Site re-checked in the browser after the reformat — theme toggle, accordion and copy buttons all still work.

🤖 Generated with Claude Code