MGR

MGR is a multi-tenant brewery operations system built on Next.js (App Router, TypeScript) and Supabase (Postgres, Auth, RLS): catalog, immutable inventory ledger, allocations/ATP, staged CSV import, staff and buyer invitations (existing accounts accept a pending invitation after signing in), orders, shipments, invoicing, the customer portal, brewing, purchasing, compliance, QuickBooks (manual payment sync), Square POS, Slack notifications, and Ask MGR chat. The staff and portal guides under content/docs/ describe what exists today.

• Documentation: content/docs/ — Fumadocs MDX served at /docs (index.mdx chooses between the staff and customer-portal guides and the HTTP API reference at /docs/api, whose operations are generated from the command registry and the screens by bun run docs:api; search at /api/search)
• Spec: .agents/superpowers/specs/2026-08-30-mgr-slice1-core-orders-design.md
• Historical plan (superseded): .agents/superpowers/plans/2026-08-30-slice1a-foundation.md
• Schema: .agents/superpowers/specs/2026-08-31-mgr-schema-design.md (tables) and 2026-08-31-mgr-schema-decisions.md (why)

Iron rules

See .agents/ARCHITECTURE.md for the ownership map and the five iron rules (commands-only, append-only ledger, RLS everywhere, admin client confined, multi-row writes are one Postgres function) and what enforces each one. Agents start at AGENTS.md.

Local development

Requires Node.js 24.x and Bun 1.3.x. The repository pins Node in .node-version and package.json, and Bun in .bun-version / packageManager; use Bun for installs and scripts, and Node 24 as the Next.js runtime.

bunx tsc --noEmit uses TypeScript 7 through the @typescript/native alias. ESLint, Next.js tooling, and screen-composition tests still need the TypeScript 6 compiler API, supplied by Microsoft’s @typescript/typescript6 compatibility package under the typescript name. It uses the official npm tarball because Bun 1.3.10 resolves the nested npm alias back to the compatibility package when the compatibility package itself is installed through an npm alias. See Microsoft’s side-by-side guidance. Node type definitions stay on the latest 24.x release to match the runtime.

Local Supabase runs on non-default ports (54341/54342/54343) configured in the committed supabase/config.toml. These ports are used by every developer and in CI — they were chosen to avoid colliding with a default-port Supabase project running alongside locally. Verify the live values with bunx supabase status:

API URL:  http://127.0.0.1:54341
DB URL:   postgresql://postgres:[email protected]:54342/postgres
Studio:   http://127.0.0.1:54343

CI (.github/workflows/ci.yml) derives env vars from bunx supabase status -o env rather than hardcoding them, so the setup automatically adapts to the values in config.toml.