feat: classify and gate publishable templates

[xiongxz]

Summary

• classify every catalog template with an immutable publishing compatibility contract
• add controlled native profiles and runtime-config bootstrapping for publishable Vite templates
• convert the Todo starter to a verified Next.js static export
• add CI admission for lockfiles, fixed build scripts, dependency install, production output, runtime config, credentials, homepage and deep-link routing

Compatibility

• Native: admin-dashboard, insight-flow-agent-chat, web-research-agent, website-change-monitor, React starter, Todo starter
• Requires Node runtime: e-commerce, landing, crm, booking, chatbot, ai-pdf-chatbot, workspace
• Generic Next.js starter remains Node-runtime-only

Validation

• npm --prefix scripts test (17 passed)
• node scripts/validate-registry.mjs (11 templates)
• real production builds and artifact admission for all 4 registry-native Vite templates
• real Vite+pnpm build for insight-flow-agent-chat
• real Next.js static-export build for Todo (out/index.html, out/404.html, 20 files)
• React starter production build and admission

Companion platform and UI PRs will be linked after creation.

---

Summary by cubic

Classifies every catalog template with an immutable publishing compatibility contract and makes native templates buildable and gated by CI. Previously templates were static references; now registry.json declares publishingCompatibility, buildProfile, and optional requiredCapabilities, and CI builds native templates and admits their production output.

Migration

• Registry entries must now declare publishingCompatibility; buildProfile is required for native entries.
• Contributors must add requiredCapabilities only for capabilities a template actually uses.

Template changes

• Chatbot starter now runs AI and storage through the Platform runtime instead of the Vercel AI Gateway; provider API keys are no longer read from app code.
• Todo starter is a verified Next.js static export with runtime-config bootstrapping.
• Adds three native Vite templates (insight-flow-agent-chat, web-research-agent, website-change-monitor) plus runtime config loading for existing native templates.
• Forks no longer trigger the production sync endpoint.

^{Written for commit 27144c1. Summary will update on new commits.}

[agent-zhang-beihai]

Thanks for the PR, @xiongxz! A quick note on our workflow: we ask contributors to open an issue first, get it assigned, then submit a PR that links it (e.g. "Closes #123"). This PR isn't linked to any issue. It'll still be reviewed, but please open an issue and claim it (comment that you'd like it assigned to you) so the work is tracked.

[xiongxz]

Companion PRs for the same delivery line:

• Publisher/platform contract: https://github.com/lexmount/insforge-platform/pull/74
• Creation UX and Agent Context: https://github.com/lexmount/insight-flow/pull/830

[xiongxz]

Closing as superseded: this PR was mistakenly opened against upstream and therefore included five pre-existing fork commits outside this delivery. The corrected one-commit, task-scoped PR targets the production fork baseline at lexmount#6. No changes from this oversized PR were merged.