@everystack/mcp 0.3.1 → 0.3.2

package/dist/index.cjs

@@ -23411,9 +23411,9 @@ var handWrittenMigration = {
   id: "hand-written-migration",
   tier: "framework",
   severity: "deny",
-  guide: "Schema and migrations are generated from your Models \u2014 edit the Model and run db:generate, never hand-write SQL migrations or edit the generated schema.",
-  conform: "everystack db:generate",
-  verify: "everystack db:generate produces no diff (a clean no-op)",
+  guide: "Schema changes have two homes, neither is a hand-written migration: tables/constraints/authz are generated from your Models (edit the Model, run db:generate); functions, views, and matviews are authored in db/sql/ and DEPLOYED with db:reconcile \u2014 no migration file either way.",
+  conform: "everystack db:generate (tables) \xB7 everystack db:reconcile (functions/views/matviews in db/sql)",
+  verify: "everystack db:generate produces no diff AND everystack db:reconcile --check exits 0",
   detect(ctx) {
     if (ctx.tool !== "Write" && ctx.tool !== "Edit") return null;
     const p = ctx.filePath;
@@ -23705,7 +23705,7 @@ async function runGovernanceCli(argv) {
 }
 
 // src/index.ts
-var version2 = (true ? "0.3.1" : null) ?? "0.3.0-dev";
+var version2 = (true ? "0.3.2" : null) ?? "0.3.0-dev";
 var INSTRUCTIONS = [
   "You govern how any agent builds everystack \u2014 a self-hosted application stack for Expo apps on AWS.",
   "Your job is not only to advise but to keep the build on-script: the architecture the maintainer",
@@ -23767,7 +23767,7 @@ var INSTRUCTIONS = [
   "1. Read everystack://core for architecture and conventions.",
   "2. Read everystack://security before any deployment or auth guidance.",
   "3. Load detail resources on demand when the user asks about specific features.",
-  "4. Data lives in PostgreSQL via Models/Modules and is served through the API \u2014 never bundle large computed data into the app. Schema changes go through generated migrations (`db:generate`), never hand-written DDL. Reuse `@everystack/ui` components; never put secret values behind `EXPO_PUBLIC_*`.",
+  "4. Data lives in PostgreSQL via Models/Modules and is served through the API \u2014 never bundle large computed data into the app. Schema changes have two homes: tables/authz are generated from Models (`db:generate`); functions, views, and matviews are authored in `db/sql/` and deployed with `db:reconcile` \u2014 never a hand-written migration either way. Reuse `@everystack/ui` components; never put secret values behind `EXPO_PUBLIC_*`.",
   '5. When the user wants to start a new project, run check_environment (phase "local" for dev, "deploy" for deployment) to verify prerequisites.',
   "6. When the user needs to interact with deployed infrastructure, guide them to use the everystack CLI."
 ].join("\n");

package/dist/project-claude-md.md

@@ -19,9 +19,12 @@ These are enforced (everystack cheat gates) and load-bearing. Do not work around
 - **Data lives in PostgreSQL, served through the API — never bundle data into the app.** A
   large `.json`/`.csv` of computed data in the bundle is wrong; model it and serve it, or
   render an empty state if it does not exist yet.
-- **Schema and migrations are generated from Models.** Declare tables with `defineModel`
-  (in `models/`), run `everystack db:generate`. Never hand-write a SQL migration, never edit
-  the generated `db/schema.ts`. After any change, `db:generate` must be a clean no-op.
+- **Schema changes have two homes; neither is a hand-written migration.** Tables and authz
+  are generated from Models: declare with `defineModel` (in `db/models/`), run
+  `everystack db:generate` — never hand-write a SQL migration, never edit the generated
+  `db/schema.ts`; after any change `db:generate` must be a clean no-op. Functions, views,
+  and matviews are **authored** in `db/sql/` and **deployed** with `everystack db:reconcile`
+  — edit the SQL file, reconcile, done; `db:reconcile --check` must exit 0.
 - **Authorization is declared, not hand-written.** Use `can()` abilities on the Model; they
   compile to RLS + grants. Never hand-write `CREATE POLICY`/`GRANT`. RLS is required.
 - **Reuse `@everystack/ui`.** Do not hand-roll a component that already exists there. Style
@@ -32,10 +35,11 @@ These are enforced (everystack cheat gates) and load-bearing. Do not work around
 
 ## Start Here
 
-- `models/` — `defineModel` tables (the source of truth for schema + authz)
+- `db/models/` — `defineModel` tables (the source of truth for schema + authz)
+- `db/sql/` — functions, views, matviews (authored SQL; deploys via `db:reconcile`)
 - `app/` — Expo Router pages (screens, navigation, API routes)
 - `server/` — Lambda handlers (api.ts, worker.ts, image.ts)
-- `db/` — generated Drizzle schema + migrations (do not edit by hand)
+- `db/schema.generated.ts`, `drizzle/` — generated artifacts (do not edit by hand)
 - `lib/` — shared code (auth context, API client)
 - `sst.config.ts` — AWS infrastructure definition
 - `docs/RUNBOOK.md` — how to operate this app; regenerate with `everystack runbook`
@@ -51,6 +55,7 @@ pnpm install                                 # Install dependencies
 pnpm dev                                     # Start the Expo dev server
 pnpm test                                    # Run all tests (TDD)
 everystack db:generate                       # Models → next migration (data + authz)
+everystack db:reconcile --apply              # Deploy functions/views/matviews from db/sql (no migrations)
 everystack db:migrate                        # Apply migrations on the deployed Lambda
 everystack db:seed                           # Seed the database (dev only)
 everystack deploy --stage dev                # Deploy infrastructure (SST)
@@ -67,7 +72,9 @@ Declare tables with `defineModel` (`field`, `can`, relations). A package's full
 `defineModule`; the app composes Modules. `everystack db:generate` compiles them to one
 migration (schema + RLS + grants); `deriveHandlerConfig(models)` derives the API config. You
 never hand-write migrations, RLS, or handler access-control — they are derived, so they cannot
-drift.
+drift. The derived layer (functions, views, matviews) is the exception that proves the rule:
+that SQL is authored, in `db/sql/`, and *deployed* with `db:reconcile` — hand-edits straight
+against the database surface as drift, and a comment-only edit is a no-op.
 
 ### Security over all else
 
@@ -96,7 +103,8 @@ Every feature starts with a failing test. Tests in `__tests__/` mirroring source
 ## What NOT to Do
 
 - Don't bundle large data into the app — it lives in the DB, served by the API.
-- Don't hand-write migrations or edit `db/schema.ts` — edit the Model, run `db:generate`.
+- Don't hand-write migrations or edit `db/schema.ts` — edit the Model, run `db:generate`;
+  for functions/views/matviews edit `db/sql/` and run `db:reconcile`.
 - Don't hand-write RLS — declare `can()` abilities.
 - Don't hand-roll a component that exists in `@everystack/ui`; don't use inline `StyleSheet`.
 - Don't put a secret behind `EXPO_PUBLIC_*` — that ships to the client.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/mcp",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Governance layer that governs how any agent builds everystack — grounding, cheat gates, and Model-aware tooling over MCP",
   "license": "AGPL-3.0-only",
   "author": "Scalable Technology, Inc. <licensing@scalable.technology>",
@@ -40,7 +40,7 @@
     "tsx": "4.21.0",
     "typescript": "5.9.3",
     "zod": "3.25.67",
-    "@everystack/cli": "0.3.12",
+    "@everystack/cli": "0.3.14",
     "@everystack/model": "0.3.4"
   },
   "scripts": {

package/src/gates/detectors/hand-written-migration.ts

@@ -5,6 +5,10 @@
  * (`db:generate`). A hand-written `.sql` migration or a hand-edit to the generated
  * `db/schema.ts` drifts the database from the Models — the migration the CLI would
  * write next is no longer a clean no-op. Pure path check; no IO.
+ *
+ * Note the layer split: SQL under `db/sql/` is the DERIVED layer (functions,
+ * views, matviews) and is legitimately authored — it deploys via `db:reconcile`,
+ * not through migrations, so this gate deliberately does not match it.
  */
 
 import { relative } from 'path';
@@ -28,9 +32,9 @@ export const handWrittenMigration: CheatGate = {
   tier: 'framework',
   severity: 'deny',
   guide:
-    'Schema and migrations are generated from your Models — edit the Model and run db:generate, never hand-write SQL migrations or edit the generated schema.',
-  conform: 'everystack db:generate',
-  verify: 'everystack db:generate produces no diff (a clean no-op)',
+    'Schema changes have two homes, neither is a hand-written migration: tables/constraints/authz are generated from your Models (edit the Model, run db:generate); functions, views, and matviews are authored in db/sql/ and DEPLOYED with db:reconcile — no migration file either way.',
+  conform: 'everystack db:generate (tables) · everystack db:reconcile (functions/views/matviews in db/sql)',
+  verify: 'everystack db:generate produces no diff AND everystack db:reconcile --check exits 0',
   detect(ctx: ToolCallContext): string | null {
     if (ctx.tool !== 'Write' && ctx.tool !== 'Edit') return null;
     const p = ctx.filePath;

package/src/index.ts

@@ -71,7 +71,7 @@ const INSTRUCTIONS = [
   '1. Read everystack://core for architecture and conventions.',
   '2. Read everystack://security before any deployment or auth guidance.',
   '3. Load detail resources on demand when the user asks about specific features.',
-  '4. Data lives in PostgreSQL via Models/Modules and is served through the API — never bundle large computed data into the app. Schema changes go through generated migrations (`db:generate`), never hand-written DDL. Reuse `@everystack/ui` components; never put secret values behind `EXPO_PUBLIC_*`.',
+  '4. Data lives in PostgreSQL via Models/Modules and is served through the API — never bundle large computed data into the app. Schema changes have two homes: tables/authz are generated from Models (`db:generate`); functions, views, and matviews are authored in `db/sql/` and deployed with `db:reconcile` — never a hand-written migration either way. Reuse `@everystack/ui` components; never put secret values behind `EXPO_PUBLIC_*`.',
   '5. When the user wants to start a new project, run check_environment (phase "local" for dev, "deploy" for deployment) to verify prerequisites.',
   '6. When the user needs to interact with deployed infrastructure, guide them to use the everystack CLI.',
 ].join('\n');

package/src/resources/project-claude-md.md

@@ -19,9 +19,12 @@ These are enforced (everystack cheat gates) and load-bearing. Do not work around
 - **Data lives in PostgreSQL, served through the API — never bundle data into the app.** A
   large `.json`/`.csv` of computed data in the bundle is wrong; model it and serve it, or
   render an empty state if it does not exist yet.
-- **Schema and migrations are generated from Models.** Declare tables with `defineModel`
-  (in `models/`), run `everystack db:generate`. Never hand-write a SQL migration, never edit
-  the generated `db/schema.ts`. After any change, `db:generate` must be a clean no-op.
+- **Schema changes have two homes; neither is a hand-written migration.** Tables and authz
+  are generated from Models: declare with `defineModel` (in `db/models/`), run
+  `everystack db:generate` — never hand-write a SQL migration, never edit the generated
+  `db/schema.ts`; after any change `db:generate` must be a clean no-op. Functions, views,
+  and matviews are **authored** in `db/sql/` and **deployed** with `everystack db:reconcile`
+  — edit the SQL file, reconcile, done; `db:reconcile --check` must exit 0.
 - **Authorization is declared, not hand-written.** Use `can()` abilities on the Model; they
   compile to RLS + grants. Never hand-write `CREATE POLICY`/`GRANT`. RLS is required.
 - **Reuse `@everystack/ui`.** Do not hand-roll a component that already exists there. Style
@@ -32,10 +35,11 @@ These are enforced (everystack cheat gates) and load-bearing. Do not work around
 
 ## Start Here
 
-- `models/` — `defineModel` tables (the source of truth for schema + authz)
+- `db/models/` — `defineModel` tables (the source of truth for schema + authz)
+- `db/sql/` — functions, views, matviews (authored SQL; deploys via `db:reconcile`)
 - `app/` — Expo Router pages (screens, navigation, API routes)
 - `server/` — Lambda handlers (api.ts, worker.ts, image.ts)
-- `db/` — generated Drizzle schema + migrations (do not edit by hand)
+- `db/schema.generated.ts`, `drizzle/` — generated artifacts (do not edit by hand)
 - `lib/` — shared code (auth context, API client)
 - `sst.config.ts` — AWS infrastructure definition
 - `docs/RUNBOOK.md` — how to operate this app; regenerate with `everystack runbook`
@@ -51,6 +55,7 @@ pnpm install                                 # Install dependencies
 pnpm dev                                     # Start the Expo dev server
 pnpm test                                    # Run all tests (TDD)
 everystack db:generate                       # Models → next migration (data + authz)
+everystack db:reconcile --apply              # Deploy functions/views/matviews from db/sql (no migrations)
 everystack db:migrate                        # Apply migrations on the deployed Lambda
 everystack db:seed                           # Seed the database (dev only)
 everystack deploy --stage dev                # Deploy infrastructure (SST)
@@ -67,7 +72,9 @@ Declare tables with `defineModel` (`field`, `can`, relations). A package's full
 `defineModule`; the app composes Modules. `everystack db:generate` compiles them to one
 migration (schema + RLS + grants); `deriveHandlerConfig(models)` derives the API config. You
 never hand-write migrations, RLS, or handler access-control — they are derived, so they cannot
-drift.
+drift. The derived layer (functions, views, matviews) is the exception that proves the rule:
+that SQL is authored, in `db/sql/`, and *deployed* with `db:reconcile` — hand-edits straight
+against the database surface as drift, and a comment-only edit is a no-op.
 
 ### Security over all else
 
@@ -96,7 +103,8 @@ Every feature starts with a failing test. Tests in `__tests__/` mirroring source
 ## What NOT to Do
 
 - Don't bundle large data into the app — it lives in the DB, served by the API.
-- Don't hand-write migrations or edit `db/schema.ts` — edit the Model, run `db:generate`.
+- Don't hand-write migrations or edit `db/schema.ts` — edit the Model, run `db:generate`;
+  for functions/views/matviews edit `db/sql/` and run `db:reconcile`.
 - Don't hand-write RLS — declare `can()` abilities.
 - Don't hand-roll a component that exists in `@everystack/ui`; don't use inline `StyleSheet`.
 - Don't put a secret behind `EXPO_PUBLIC_*` — that ships to the client.