feat(create-ideal-cms): add npx scaffolding CLI

[dogfrogfog]

Summary

• Introduce @focus-reactive/create-ideal-cms — an npx-runnable CLI that scaffolds a Payload + Next.js monorepo from this repo's apps/cms template, pinning the @focus-reactive plugin suite as published npm deps.
• Add source-side overrides so consumers of the published plugins don't get a flood of peer-warning noise (single source of truth for react, react-dom, @payloadcms/plugin-mcp, @modelcontextprotocol/sdk versions).
• Bump @payloadcms/plugin-mcp 3.84.0 → 3.84.1 in apps/cms to align with payload 3.84.1.
• Pick up in-progress UI tweaks across apps/cms/src/... and packages/ui/components/... from pending working-tree state.

What the CLI does

Interactive prompts:

• Project name → target directory
• Brand color (hex, applied as a --color-primary overlay in packages/tailwind-config/base.css)
• Postgres DATABASE_URL, NEXT_PUBLIC_SERVER_URL
• Optional OpenAI / Vercel Blob / OIDC tokens
• Git init + package manager (bun/pnpm/npm/skip)
• Optional initial DB migration

Under the hood:

• Fetches the monorepo via giget (GitHub tarball) or copies a local checkout with --from-local
• Prunes plugin source packages, the dev sandbox, release machinery, lockfile
• Rewrites workspace:* plugin refs in apps/cms/package.json to pinned published versions
• Empties the migrations dir + stubs it, runs payload migrate:create init post-install
• Auto-generates PAYLOAD_SECRET; writes OPENAI_API_KEY placeholder so the translator plugin instantiates cleanly without a real key

Test plan

• bun run lint — clean (0/0)
• bun run check-types — clean (pre-push hook passed)
• bun run build in packages/create-ideal-cms — outputs 16 KB ESM with shebang
• bun run test:local — scaffolds into .test-output/<name>/, install + migration run cleanly
• Fresh scaffold bun install — 0 peer warnings (verified)
• After merge: first manual npm publish --access public (one-time) → configure npm Trusted Publisher → gh release create @focus-reactive/create-ideal-cms@1.0.0 → push docs commit to let CI auto-publish 1.0.1

Follow-ups (post-merge, see payload-plugins-add-package skill)

1. From packages/create-ideal-cms/ run npm publish --access public
2. On npmjs.com → @focus-reactive/create-ideal-cms → Publishing → add Trusted Publisher (focusreactive/payload-plugins + release.yml + main)
3. gh release create "@focus-reactive/create-ideal-cms@1.0.0" --target <merge-commit-sha> --title "create-ideal-cms v1.0.0" --notes "Initial release"
4. Push a docs: commit touching the package → CI publishes 1.0.1 automatically

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
turbo-cms-kit-payload	Error		May 25, 2026 2:24pm