bigin-harness-setuplisted

# bigin-harness-setup Sets up a standardized AI workflow harness — the `CLAUDE.md` agent brief, path-scoped rules, and commit-time enforcement gates (guard hooks + a context-budget check). Idempotent — re-running on an already-set-up repo is safe. --- ## Phase 0: Detect Stack Profile Check for stack indicators: 1. `nuxt.config.ts` or `nuxt.config.js` → profile = `nuxt` 2. `go.mod` → profile = `go` 3. `package.json` with express/fastify/hono/koa in dependencies → profile = `nodejs` 4. `next.config.ts`, `next.config.js`, or `next.config.mjs` → profile = `next` 5. None found or ambiguous → ask: ``` Which stack profile? 1. nuxt — Nuxt 4 fullstack (Cloudflare Pages): Nuxt UI, Pinia + Colada, VueUse, nuxt-auth-utils, Vitest, Zod — BFF proxy layer, no direct DB access 2. go — Go REST API backend 3. nodejs — Node.js TypeScript REST API backend 4. next — Next.js App Router fullstack (Vercel): shadcn/ui, Zustand, TanStack Query, iron-session, Vitest, Zod — BFF proxy layer, no direct DB access Type 1, 2, 3, or 4. ``` Store result as `PROFILE`. Load `references/profile-{PROFILE}.md` for all template content. --- ## Phase 0.5: Project Scaffold (empty repo only) Runs when the repo lacks the marker file for `PROFILE` — `nuxt.config.ts` (nuxt), `next.config.*` (next), `go.mod` (go), `package.json` (nodejs). Skip the phase entirely otherwise; that's onboarding an existing repo. Scaffolding is delegated to that profile's own skill and its deterministic script — **not** done