rcode-migratelisted

@.rcode/references/karpathy-guidelines.md ## Overview MVPs are built to ship — corners get cut by design. Past a certain user count or revenue threshold, those cuts become tax: every new feature gets harder, every deploy is scary, every bug takes a day to root-cause. This skill plans the graduation in phases that ship continuously, never with a "we'll rewrite the whole thing" big bang. ## Workflow 1. **Audit the gaps.** Run a 30-minute MVP-vs-production gap report against the eight checks below. 2. **Triage by blast radius.** Which gap, if it stays, kills the next 3 sprints? Fix that one first. Cosmetic gaps wait. 3. **Plan in 1-week increments.** Each increment must leave the system shippable. No "we'll come back to fix this in 2 weeks" half-states. 4. **Bring the team along.** New patterns get documented in `decisions.md` and `glossary.md` so the next dev finds them. 5. **Each increment closes with a smoke-test deploy** and a metric showing the improvement. ## The eight production checks For each: pass / partial / fail. "Partial" means it exists but isn't enforced; treat as fail for planning. 1. **Tests.** Unit + integration + at least one end-to-end happy-path test, all running in CI on every PR. 2. **CI/CD.** Push-to-deploy on a PR-merge basis, with a manual approval gate to production. 3. **Observability.** Errors land in Sentry (or equivalent) within 30s. Latency p95 graph exists. Logs are searchable. 4. **Authentication.** Real provider (Keycloak, Auth0, Clerk,