Merge branch 'main' into feat/eql-v3-text-search-schema

Reconciles the parallel EQL v3 evolution on both sides. The branch side
carried the newer stack surface (bigint domain family, freeTextSearch
tuner removal, DOMAIN_REGISTRY, supabase adapter with introspection and
or()-string hardening, null-prototype column maps, grants.ts extraction);
the main side carried the newer CLI (registry-driven help + manifest,
decoupled eql install / offerStashConfig, one-shot --database-url,
eql upgrade/status group), auth 0.41 Result API + authStrategy rename,
generation-aware isInstalled, and the eql-3.0.0-alpha.2 vendored bundle.

Resolution notes:
- stack src/tests: branch side kept; authStrategy rename and its wasm
  latch taken from main; Plaintext keeps the branch bigint arm.
- encrypt-lock-context-guards now builds one client per wire format
  (main's mixed-schema guard rejects a shared client).
- EncryptionV3 pins eqlVersion 3 (branch semantics); the main-side
  override test now asserts the pin.
- supabase-v3.test.ts (main) removed: superseded by the branch's
  supabase-v3-pgrest-live/matrix/grants/introspect suites on the
  contains() surface.
- query-builder.ts: dropped main's apply-time filterColumnName calls in
  favour of the branch's translate-once-at-toDbSpace boundary; removed
  main's orphaned {select,keyToDb} addJsonbCastsV3 twin.
- SQL bundles/fixture: main's alpha.2 copies for now — re-vendored to
  eql-3.0.0 in the follow-up FFI 0.29 upgrade.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: calvinbrewer

.changeset/native-binary-guards.md

@@ -0,0 +1,12 @@
+---
+'@cipherstash/prisma-next': minor
+---
+
+Upgrade to Prisma Next 0.14.0 (from 0.8.0). Every `@prisma-next/*` dependency is now pinned at 0.14.0; consuming apps must run Prisma Next 0.14 to use this release.
+
+Highlights of the upgrade:
+
+- The extension contract space is re-emitted in the 0.14 canonical shape: storage is namespace-enveloped (`storage.namespaces.public.entries.table`), the domain plane replaces flat `models`, and the baseline EQL-install migration is re-pinned to the new storage hash. The vendored EQL bundle SQL is unchanged byte-for-byte.
+- `deriveStackSchemas` reads the namespace-enveloped contract shape emitted by Prisma Next 0.10+.
+- The bulk-encrypt middleware accepts the widened insert/update AST value unions introduced through 0.9–0.11.
+- README examples use the namespace-qualified ORM accessors (`db.orm.public.User`) required since Prisma Next 0.14.

.changeset/prisma-next-0-14.md

@@ -0,0 +1,22 @@
+---
+"@cipherstash/stack": patch
+"stash": patch
+---
+
+Remove the leftovers from the secrets removal (`1929c8fe`), which deleted
+`packages/stack/src/secrets/` but left its export, build entry, skill, and docs
+behind. Secrets tooling is not ready; nothing here was functional.
+
+- **Drop the dead `@cipherstash/stack/secrets` subpath export.** It pointed at
+  `./dist/secrets/index.js`, which has no source and is not in the tarball, so
+  `import '@cipherstash/stack/secrets'` has been throwing `ERR_MODULE_NOT_FOUND`
+  for every consumer since the source was removed. Also drops the dangling
+  `src/secrets/index.ts` entry from `tsup.config.ts`. Removing an export that
+  cannot resolve breaks nothing.
+- **Remove the `stash-secrets` agent skill** and its references in `AGENTS.md`
+  and the init setup-prompt skill index. It was never installed by `stash init`
+  (it is absent from `SKILL_MAP`), so no user project ever received it.
+- **Remove the secrets documentation** from both published READMEs: the
+  `Secrets` class API and the `npx stash secrets` command reference in
+  `@cipherstash/stack`, and the `npx stash secrets` section in `stash`. The CLI
+  command does not exist — `stash secrets` returns `Unknown command`.

.changeset/remove-secrets-leftovers.md

@@ -0,0 +1,31 @@
+---
+"stash": patch
+---
+
+Refresh the bundled `stash-cli` agent skill and the CLI README against the current
+command surface. The skills directory ships inside the `stash` tarball and is copied
+into the user's `.claude/skills/` / `.codex/skills/` (or inlined into `AGENTS.md`) at
+handoff time, so a stale skill becomes stale guidance in the user's project.
+
+- **New `Start here` and `Authentication` sections.** Setup is driven through the CLI:
+  agents read `stash manifest --json` first, then trigger `stash auth login --json` and
+  surface the verification URL for a human to approve, then run `stash init`. Authenticating
+  before `init` matters — `init`'s auth step is interactive and would otherwise try to open
+  a browser on the agent's host.
+- **New `Never read these` invariant**, mirrored into the `AGENTS.md` doctrine: agents must
+  never read `~/.cipherstash/secretkey.json`, `~/.cipherstash/auth.json`, anything under
+  `~/.cipherstash/workspaces/`, or `.env*`. The wizard already blocks these paths in code;
+  the other handoff targets had no written rule.
+- **Documents `manifest`, `doctor`, `wizard`, and `auth regions`**, which the skill omitted
+  entirely, plus the non-interactive interface (per-command escape hatches, exit codes, the
+  `DATABASE_URL` resolution order, the `auth login --json` NDJSON event contract).
+- **Corrects the `db` → `eql` move.** `db install`, `db upgrade`, and `db status` are
+  deprecated aliases that warn and forward; `db push`, `db activate`, `db validate`,
+  `db test-connection`, and `db migrate` remain in the `db` group.
+- **Scopes `db push` / `db activate` as EQL v2 + CipherStash Proxy only**, in both the skill
+  and the README's recommended flow. SDK users hold their encryption config in application
+  code and don't need them.
+- Adds the missing `--database-url`, `--eql-version`, `--prisma-next`, `--proxy`/`--no-proxy`,
+  and `--region` flags; corrects six programmatic API signatures; fixes the README's claim
+  that `stash init` ends in an agent-handoff menu (that belongs to `stash plan` / `stash impl`);
+  and marks `stash env` as the non-functional stub it currently is.

.changeset/stack-protect-ffi-0-26-oidc-strategy.md

@@ -0,0 +1,18 @@
+---
+"@cipherstash/wizard": patch
+---
+
+Stop the agent guard from blocking `.env.example`.
+
+`SENSITIVE_FILE_PATTERNS` matched `/\.env($|\.)/`, which tests true against
+`.env.example`. Because the guard covers `Edit` and `Write` as well as `Read`,
+the wizard's agent was blocked from creating or editing the very file the
+CipherStash doctrine tells it to write ("New env keys go in `.env.example` with
+placeholders"). Committed env templates carry placeholder key names, not values.
+
+`.env.example`, `.env.sample` and `.env.template` are now readable and writable.
+Everything else is unchanged: `.env`, `.env.local`, `.env.production`, and
+value-bearing files that merely start with a template name
+(`.env.example.local`, `.env.example.bak`) stay blocked, as do `auth.json`,
+`secretkey.json` and credential files. Bash access to any env file — including
+the templates — remains blocked; `Read`/`Write` is the sanctioned path.

.changeset/stash-cli-skill-refresh.md

@@ -1,10 +1,11 @@
-# Cursor Super-Prompt: Protect.js Example Apps (Framework/ORM-Agnostic, No-Cheese)
+# Cursor Super-Prompt: CipherStash Stack Example Apps (Framework/ORM-Agnostic, No-Cheese)
 
 ROLE
-You are a senior systems engineer focused on developer experience and a core maintainer of `@cipherstash/protect`. Your mission: create a polished set of runnable **Protect.js example apps** across multiple stacks. Each example must be minimal, factual, and runnable in minutes.
+You are a senior systems engineer focused on developer experience and a core maintainer of `@cipherstash/stack`. Your mission: create a polished set of runnable **CipherStash Stack example apps** across multiple stacks. Each example must be minimal, factual, and runnable in minutes.
 
 GROUNDING & SOURCES (use @ref; do not guess)
-- Protect.js APIs: the Protect.js main README is the single source of truth. If not accessible, STOP and ask for the exact snippet/repo path. Do not invent APIs.
+- Stack APIs: the main repo README and https://cipherstash.com/docs are the source of truth (`Encryption({ schemas })`, `encryptedTable`, `encryptedColumn`). If not accessible, STOP and ask for the exact snippet/repo path. Do not invent APIs.
+- `@cipherstash/protect-ffi` is a native Node-API module: examples that bundle (Next.js, SST) must externalize it. See https://cipherstash.com/docs/stack/deploy/bundling
 - ORM/DB docs (pick per stack):  
   @ref https://www.prisma.io/docs  
   @ref https://typeorm.io  
@@ -26,7 +27,7 @@ STACK MATRIX (generate now)
 Optional (time-permitting): nextjs-prisma (App Router), fastify-knex.
 
 NO-CHEESE RULES (hard requirements)
-Goal: smallest possible working example that clearly demonstrates Protect.js. Clarity > patterns > abstractions.
+Goal: smallest possible working example that clearly demonstrates CipherStash Stack. Clarity > patterns > abstractions.
 DON'TS
 - No Singletons/Factories/Service-Locators/DI frameworks.
 - No ports & adapters/custom repo abstractions for tiny demos—call the ORM/client directly.
@@ -41,7 +42,7 @@ README tone
   ---
 Simplicity budget (per example)
 - ≤ 8 TS source files (excluding migrations).
-- Deps: ORM/client + `@cipherstash/protect` + dev tooling (ts-node or tsx). Nothing else unless required by the stack.
+- Deps: ORM/client + `@cipherstash/stack` + dev tooling (ts-node or tsx). Nothing else unless required by the stack.
 - One `.env.example`; use `dotenv`. No layered config.
 
 CODE STYLE
@@ -61,8 +62,8 @@ REQUIRED DX & SCRIPTS (per example)
   - `seed` → seed sensible data
   - `demo` → prints proof of encryption & queries
   - `typecheck` → `tsc --noEmit`
-- `.env.example` includes DB vars and **exact** Protect.js env names from the Protect README (do not invent):
-  {{PROTECT_ENV_VARS := "e.g., PROTECT_PROJECT_ID, PROTECT_CLIENT_KEY, PROTECT_SERVER_URL (replace with real names from README)"}}
+- Local dev auth: prefer the CipherStash profile via `npx stash auth login` (no env vars needed). For CI/deployment, `.env.example` includes DB vars and the **exact** CipherStash env names (do not invent):
+  `CS_WORKSPACE_CRN`, `CS_CLIENT_ID`, `CS_CLIENT_KEY`, `CS_CLIENT_ACCESS_KEY`
 
 PROJECT LAYOUT (monorepo, minimal)
 - Root:
@@ -80,10 +81,10 @@ README REQUIREMENTS (every example)
 - AI banner (exact text) at the very top with {{BOOK_CHAT_URL}}.
 - 90-second Quickstart (copy/paste only).
 - "What this shows" checklist (encrypted fields, CRUD, query).
-- "How encryption works here" (short, accurate, tied to Protect.js).
+- "How encryption works here" (short, accurate, tied to CipherStash Stack).
 - Config notes for the stack (e.g., why CJS for TypeORM).
-- Troubleshooting (ESM/CJS, ts-node/tsx, migration pitfalls).
-- `@ref` links to stack docs + Protect README.
+- Troubleshooting (ESM/CJS, ts-node/tsx, migration pitfalls, native module externalization).
+- `@ref` links to https://cipherstash.com/docs + the repo README.
 
 DELIVERABLES (return in one message/PR)
 - Root `README.md` + `docker-compose.yml`.
@@ -118,4 +119,3 @@ OUTPUT FORMAT
 VARIABLES TO FILL BEFORE RUN
 - {{BOOK_CHAT_URL}} = your booking link
 - {{STACKS}} = list of stacks to generate
-- {{PROTECT_ENV_VARS}} = exact names from Protect.js README

.changeset/wizard-allow-env-templates.md

@@ -35,7 +35,7 @@ body:
     id: terms
     attributes:
       label: Code of conduct
-      description: By submitting this issue, you agree to follow our [Code of conduct](https://github.com/cipherstash/protectjs/blob/main/CODE_OF_CONDUCT.md). 
+      description: By submitting this issue, you agree to follow our [Code of conduct](https://github.com/cipherstash/stack/blob/main/CODE_OF_CONDUCT.md). 
       options:
         - label: I agree to follow this project's Code of conduct
           required: true

.cursor/commands/create-example-app.md

@@ -78,6 +78,14 @@ jobs:
       - name: Test — lint script self-tests
         run: pnpm run test:scripts
 
+      # The EQL v3 bundles in packages/cli/src/sql are vendored (derived from
+      # the stack fixture monolith by gen:eql-v3-sql). Regenerate and fail on
+      # any diff so the fixture and the shipped bundles cannot drift silently.
+      - name: Check — vendored EQL v3 SQL bundles are in sync
+        run: |
+          pnpm --filter stash run gen:eql-v3-sql
+          git diff --exit-code -- packages/cli/src/sql/cipherstash-encrypt-v3.sql packages/cli/src/sql/cipherstash-encrypt-v3-supabase.sql
+
       - name: Create .env file in ./packages/protect/
         run: |
           touch ./packages/protect/.env