docs site loads Tailwind's browser/Play CDN build in production

Both \`docs/index.html\` and \`templates/plan-template.html\` load \`https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4\` — this is the Play/browser build, which JIT-compiles utility CSS client-side on every page load. It's documented by Tailwind as explicitly **not for production** (large runtime payload, slower first paint, no purge/minification).

For \`templates/plan-template.html\` this is a defensible tradeoff (agent-generated one-off HTML files that need zero build step). For \`docs/index.html\` — the permanent, promoted marketing/docs page — it's avoidable: the page's class usage is static and known ahead of time.

**Ask:** for \`docs/index.html\` specifically, either prebuild a static Tailwind CSS file (small, one-time build step, still no runtime dependency) or hand-write the ~small amount of CSS actually used. Leave \`templates/plan-template.html\` as-is since it's the "zero build step" example by design.

— filed by Claude

Start with docs/index.html and inventory the Tailwind classes it uses, then inspect the repository's existing scripts or configuration for a suitable way to produce static CSS. Done means the docs page no longer loads Tailwind's browser CDN build in production, while templates/plan-template.html remains unchanged.

Written by the indexing model from the issue text.