@voltro/cli 0.33.0 → 0.35.0

package/templates/agent-docs/local-first-mobile.md

@@ -23,11 +23,13 @@ imports it directly. The React wrappers live behind `@voltro/local-first/react`
 > [`crdtText()` database column](#the-crdttext-database-column) (with its
 > authoritative server-side merge on the write path), the
 > [`SyncClient`](#the-syncclient-bi-directional-wire) that drives the queue over a
-> transport, [presence/awareness](#presence--awareness) via `usePresence`,
-> [durable IndexedDB persistence](#durable-persistence), and the
+> transport, [`useCrdtText`](#a-collaborative-text-field-usecrdttext) — the React
+> binding for a collaborative text field — [presence/awareness](#presence--awareness)
+> via `usePresence`, [durable IndexedDB persistence](#durable-persistence), and the
 > [`localFirst` table mixin](#the-localfirst-table-mixin). What remains is a thin
 > [runtime binding](#whats-shipped-vs-a-runtime-seam) to provisioned infra
-> (a broker at scale, a running app's transport) — not un-built framework code.
+> (a broker at scale) plus the two app-specific tags `useCrdtText` is pointed at —
+> not un-built framework code.
 
 ## CRDT text: `crdtText` + `mergeCrdtStates`
 
@@ -139,6 +141,69 @@ Everything below the two transport functions — the drain loop, retry/attempt
 counting, optimistic local merge, durable persistence — is in the client and
 tested against an in-memory dispatcher that mirrors the server's merge.
 
+## A collaborative text field: `useCrdtText`
+
+`useCrdtText` is the React binding over that wire — one `crdtText()` cell, bound
+to the mutation that writes it and the reactive query that streams it:
+
+```tsx
+import { useMutation, useSubscription } from '@voltro/client'
+import { useCrdtText } from '@voltro/local-first/react'
+
+function BodyEditor({ id }: { id: string }) {
+  const row = useSubscription<{ body: Uint8Array | null }>('app', 'documents.byId', { id })
+  const save = useMutation<{ id: string; body: Uint8Array }>('app', 'documents.setBody')
+
+  const body = useCrdtText({
+    cell: { table: 'documents', id, column: 'body' },
+    remote: row.data?.body ?? null,             // what the server currently holds
+    push: (w) => save.mutate({ id: w.id, body: w.update }),  // deliver a local edit
+  })
+
+  return (
+    <>
+      <textarea value={body.text} onChange={(e) => body.setText(e.target.value)} />
+      {body.synced ? null : <em>saving… ({body.outstanding})</em>}
+    </>
+  )
+}
+```
+
+The hook owns one `SyncClient` per `(table, id, column)` cell — created and
+closed with the component — re-renders on a local edit, an ack or incoming
+merged state, and folds the streamed row back in. It returns `text`,
+`insert(index, text)`, `delete(index, length)`, `setText(next)`, the encoded
+`state`, `outstanding` / `synced`, and `setOnline`.
+
+<Callout type="warn">
+**`setText` is a span diff, and that is the whole point.** A `<textarea>` hands
+you the entire new string, so the obvious binding is "clear the document,
+insert the new text" — a delete-all/insert-all, which is exactly the
+last-write-wins behaviour a CRDT is chosen to prevent: two people typing in
+different paragraphs each erase the other's, and the text looks right on
+whichever peer typed last. `useCrdtText` diffs the common prefix and suffix and
+emits ONE delete plus ONE insert, so an edit outside the changed span survives.
+The diff is exported as `crdtTextEdit(before, after)` if you drive the document
+yourself.
+</Callout>
+
+Two things stay yours to name, because nothing can derive them: **which
+mutation** writes the column and **which query** streams the row. Voltro
+generates no per-table CRUD surface, so the hook takes those two as `push` and
+`remote` — the same shape as `usePresence`'s injected channel. Everything under
+them (client lifecycle, optimistic merge, offline queue, bounded retry, durable
+persistence, the edit encoding) is framework code.
+
+The descriptors on the other end declare the column as bytes-over-base64 —
+`Uint8Array` in the handler, a base64 string on the wire:
+
+```ts
+import { Schema } from 'effect'
+
+// documents.byId output (and documents.setBody input)
+body: Schema.NullOr(Schema.Uint8ArrayFromBase64)
+```
+
 ## Presence & awareness
 
 `usePresence(roomId, self, { channel })` publishes this peer's ephemeral state
@@ -168,6 +233,16 @@ Redis/NATS at scale (both already shipped). `createInMemoryPresenceChannel()` is
 the local/test transport. Join/leave, announce-back discovery, cursor
 propagation, and TTL expiry live in the pure `createPresenceRoom` the hook wraps.
 
+> **Two different hooks share the name `usePresence`, and they are not
+> interchangeable.** THIS one (`@voltro/local-first/react`) is peer-to-peer
+> awareness over a pub/sub channel — `usePresence(roomId, self, { channel })` →
+> `{ presence, others, setPresence }` — for high-frequency cursor/selection
+> state that must never touch the database.
+> [`@voltro/plugin-presence`](/docs/plugins/presence)'s is a server-backed
+> roster — `usePresence(channel, options)` → the list of members whose heartbeat
+> is fresh, plus a `useTyping` indicator, through the app's own rpc. Reach for
+> the plugin for "who is here"; reach for this one for "where is their cursor".
+
 ## The offline sync queue
 
 `useSyncQueue()` is a reactive view over a **pure, tested reducer**: writes made
@@ -252,7 +327,7 @@ code already speaks:
 
 | Runtime seam | What it binds | Why it's a binding, not code |
 | --- | --- | --- |
-| **Sync transport → a running app** | The `SyncClient`'s `push`/`onRemoteState` to one app's `useMutation` + `useSubscription`. | The two functions are app-specific glue; the drain loop, merge, retry, and persistence all ship and are tested. |
+| **Two app-specific tags** | Which mutation writes the `crdtText()` column, and which reactive query streams the row, in [`useCrdtText`](#a-collaborative-text-field-usecrdttext). | Voltro generates no per-table CRUD surface, so there is nothing to derive them from. The client lifecycle, optimistic merge, offline queue, retry, persistence and edit encoding all ship. |
 | **Presence channel → a broker at scale** | The `PresenceChannel` to a provisioned Redis/NATS broker. | It's a network hop over an already-shipped broker; the awareness logic ships and is tested over the in-memory channel. |
 | **wa-sqlite / Turso adapter** *(optional)* | A SQL durable adapter for cross-tab queries, behind `PersistenceAdapter`. | IndexedDB is the durable default today; a SQL backing is a sibling factory, nothing above it changes. |
 

package/templates/agent-docs/multi-tenancy.md

@@ -11,7 +11,7 @@
 
 _Multi-tenancy as a runtime primitive — the tenant() mixin, ctx.subject.tenantId, automatic read scoping, explicit write gates._
 
-Multi-tenancy is one of those features every B2B SaaS re-derives badly. Voltro treats it as a runtime primitive: drop the `tenant()` mixin on a table, and the framework guarantees cross-tenant data leakage is structurally impossible for **reads**. Writes get a typed `TenantMismatch` error if you forget the explicit check.
+Multi-tenancy is one of those features every B2B SaaS re-derives badly. Voltro treats it as a runtime primitive: drop the `tenant()` mixin on a table, and the framework makes cross-tenant access structurally impossible for **reads and writes alike** — including a write keyed by a row id that came straight from request input.
 
 ## The model
 
@@ -19,18 +19,27 @@ Multi-tenancy is one of those features every B2B SaaS re-derives badly. Voltro t
        Subject (tenantId: 'acme')
               │
               ▼
-   ┌─────────────────────────┐
-   │  Queries (read)          │  ← runtime AND-merges
-   │   ctx.store.select(...) │     WHERE tenantId = subject.tenantId
-   └─────────────────────────┘
-   ┌─────────────────────────┐
-   │  Mutations (write)      │  ← you call
-   │   ctx.store.insert(...) │     assertOwnTenant(input.tenantId, subject)
-   └─────────────────────────┘
+   ┌──────────────────────────────┐
+   │  Reads                        │  ← AND-merged
+   │   select / query / subscribe  │     WHERE tenantId = subject.tenantId
+   └──────────────────────────────┘
+   ┌──────────────────────────────┐
+   │  Inserts                      │  ← auto-stamped from the subject,
+   │   store.insert(...)           │     refused when there is no tenant
+   └──────────────────────────────┘
+   ┌──────────────────────────────┐
+   │  Set-based writes             │  ← AND-merged onto your WHERE
+   │   updateMany / deleteMany     │     (same predicate as reads)
+   │   update(t).where(...)        │
+   └──────────────────────────────┘
+   ┌──────────────────────────────┐
+   │  Keyed-by-id writes           │  ← the row is RESOLVED inside your
+   │   store.update(t, id, patch)  │     tenant first; TenantRowNotFound
+   │   store.delete(t, id)         │     when it isn't there
+   └──────────────────────────────┘
 ```
 
-Reads are auto-scoped because the subject + table mixin contain enough information.
-Writes are NOT auto-scoped because the input gets to *propose* a tenant — your code decides whether to honour it (typical: never) or assert against the subject (typical: always).
+Every path is enforced by the framework, not by remembering a helper. The keyed row was the last one that wasn't: `update(table, id, patch)` addressed the row by primary key alone, so a mutation that took an id from request input could write into another tenant with no error and nothing in the code to review.
 
 ## What's in this section
 
@@ -54,7 +63,11 @@ export const notes = table('notes', {
 Query (auto-scoped):
 
 ```tsx
-export const listNotes = defineQuery({ name: 'notes.list', input: Schema.Struct({}) })
+export const listNotes = defineQuery({
+  name: 'notes.list',
+  guards: [{ scope: 'notes:read' }],   // WHO may open it; tenant() decides WHICH rows
+  input: Schema.Struct({}),
+})
 export default async (_input, ctx) => ctx.store.select('notes').all()
 // SQL: SELECT * FROM notes WHERE tenantId = $1   (with subject.tenantId)
 ```
@@ -66,6 +79,7 @@ import { assertOwnTenant, TenantMismatch } from '@voltro/plugin-multitenancy'
 
 export const createNote = defineMutation({
   name:  'notes.create',
+  guards: [{ scope: 'notes:write' }],
   input: Schema.Struct({ tenantId: Schema.String, title: Schema.String }),
   error: TenantMismatch,
 })
@@ -77,13 +91,40 @@ export default async (input, ctx) => {
 
 If a client posts `{ tenantId: 'their-tenant', title: 'hack' }` while their cookie's subject says `tenantId: 'acme'`, the mutation throws `TenantMismatch`. The audit log records it; the client sees a typed error variant.
 
-## Why the asymmetry
+**`guards:` and `tenant()` answer different questions, and both descriptors above need the first one.** `tenant()` decides **which rows** a call may touch; `guards:` decides **who may make the call at all** — and a wire-exposed procedure that declares neither `guards:`, `openAccess: '<reason>'` nor `internal: true` is refused at boot. Tenant scoping is not a substitute: it confines an *anonymous* caller to whatever tenant the request resolved to, which shapes the result rather than authorizing anybody. Get both, and a revoked membership also stops an open subscription mid-session, because guards are re-checked on every delivery. Full rules: [Authorization](/docs/authentication/authorization#every-procedure-decides-guards-or-openaccess).
+
+## What a keyed write does now
+
+A keyed write resolves its target row inside `subject.tenantId` before it writes. When there is no such row, it fails with `TenantRowNotFound` from `@voltro/runtime` — it does **not** return `null` / `false`:
+
+```ts
+// notes.rename.mutation.server.ts — `input.id` comes from the client
+export default async (input, ctx) => {
+  // Another tenant's note id → TenantRowNotFound. Nothing to remember.
+  return ctx.store.update('notes', input.id, { title: input.title })
+}
+```
+
+```ts
+import { TenantRowNotFound } from '@voltro/runtime'
+// declare it to surface the refusal typed at the client
+export default defineMutation({
+  name: 'notes.rename',
+  guards: [{ scope: 'notes:write' }],
+  input: RenameInput,
+  error: TenantRowNotFound,
+})
+```
+
+**The error is deliberately ambiguous, and that is the design.** It is raised identically whether the row does not exist at all or belongs to another tenant, and it carries nothing that separates the two. Reporting "forbidden" for a foreign row and "not found" for a missing one would turn every keyed write into a cross-tenant *existence oracle*: a caller walks ids and learns which are real in someone else's tenant. Failing loudly and identically gives your handler a signal to act on and gives an attacker one bit they already had — the id they themselves sent is not theirs.
 
-Reads always have a single answer: "what does this subject see?" → AND the tenant. Auto-scopable.
+The alternative — silently affecting zero rows — is worse than either. It reads to the handler as "the row is gone" rather than "you may not touch it", so a genuine isolation breach shows up as a confusing empty branch and never as a security signal.
 
-Writes have an open question: "which tenant should this go in?" The input gets to claim — sometimes legitimately (impersonation by an admin, switching active tenant). Your code decides whether to honour the claim. The framework can't auto-enforce because legitimate exceptions exist.
+## What is NOT auto-decided: which tenant an insert claims
 
-Defaulting to "auto-reject mismatching writes" would still work for 99% of mutations + would make the 1% impossible. We picked "assert explicitly" instead — slightly more code, full flexibility.
+The open question is only ever on the way IN. An insert that omits `tenantId` is stamped from the subject; an insert that *sets* one is not silently substituted, because a legitimate cross-tenant write exists (admin tooling, impersonation). That is where `assertOwnTenant` earns its place — it rejects a *claimed* `input.tenantId` that isn't the subject's, at the top of the executor and with a typed `TenantMismatch`. It is an ergonomic early check, no longer the thing standing between you and a cross-tenant write.
+
+A genuine cross-tenant write runs as the system subject via `runAsSystem` (see [Edge cases](/docs/multi-tenancy/edge-cases)) — a subject with `tenantId: null`, for which every merge above is skipped by construction.
 
 ## Tenant scoping covers more than just the database
 
@@ -117,6 +158,20 @@ export default {
 
 Or via env — `VOLTRO_TENANT_ISOLATION=namespace` — which overrides the config field. The same flag is read by `voltro dev` and `voltro serve`, so the topology can't drift between dev and prod.
 
+### Provisioning — a new tenant's first request creates its namespace
+
+The namespace is provisioned **lazily, on first use**: a tenant nobody has seen
+before gets its schema and tables created — and its
+[`lifecycle: 'onTenantCreate'` seeds](/docs/data/queries) fired — the first time
+a request touches its store, memoised per process afterwards. There is nothing
+to pre-register, and a failed provision is retried on the next request rather
+than cached.
+
+Eager provisioning is **your** move, because only your app knows its tenants:
+call `provisionTenantNamespace(tables, namespace, sqlLayer, dialect)` from a
+seed or startup file over your own tenant table when you want the DDL paid at
+deploy time instead of on a tenant's first request.
+
 ### One mechanism, per-dialect mapping
 
 Namespace isolation is **one** mechanism — a per-request namespace `tenant_<sanitised-id>`, derived from `subject.tenantId` — mapped to each dialect's native physical container:
@@ -129,9 +184,25 @@ Namespace isolation is **one** mechanism — a per-request namespace `tenant_<sa
 
 Database-per-tenant falls out of the same seam for free — only the namespace id differs; the mapping to a physical container is a per-dialect detail. Isolation is **physical**: it no longer depends on a predicate being present, so a query that forgets the tenant filter — or a table that never carried the `tenant()` mixin at all — still cannot read another tenant's rows.
 
-### Postgres fast-path — `SET LOCAL search_path`
+### Postgres — reads are one statement, writes take a `SET LOCAL search_path` transaction
+
+On postgres a namespaced **read** compiles the namespace straight into the identifier — `"tenant_<id>"."todos"` — and runs as a single statement outside any transaction. That is the same mechanism the other dialects have always used, and it is one round trip.
+
+A namespaced **write** (and `raw()`) still runs inside a transaction whose first statement is `SET LOCAL search_path TO "tenant_<id>"`. Because it's `SET LOCAL` (transaction-scoped), the setting **resets at commit** — mandatory on a pooled connection, where a bare `SET search_path` would persist and leak into the next request that checks out the same connection. A write wants its transaction anyway; `raw()` executes SQL text you wrote, which the framework cannot qualify on your behalf.
 
-On postgres each request runs inside a transaction whose first statement is `SET LOCAL search_path TO "tenant_<id>"`. Because it's `SET LOCAL` (transaction-scoped), the setting **resets at commit** — mandatory on a pooled connection, where a bare `SET search_path` would persist and leak into the next request that checks out the same connection. The other dialects qualify identifiers directly (`tenant_<id>.todos`).
+Reads used to take the transaction too, which made every tenant read `BEGIN` + `SET LOCAL` + `SELECT` + `COMMIT` — four round trips holding one pooled connection for all four. Measured against a local postgres, that cost **2.2×** a shared-schema read, and the same factor applied to how long the connection was held, so effective pool capacity under tenant isolation was materially lower than the pool size suggested. Qualifying the identifier also removes the leak surface rather than managing it: nothing is set on the connection, so there is nothing to reset.
+
+One consequence worth knowing: an **eager** (`with:`) read under namespace isolation uses the portable multi-query walker rather than the single-roundtrip JSON aggregate, because the JSON-aggregate compiler does not qualify relation tables. That has always been true on mysql / mssql / sqlite; postgres now matches them. It shows up as `voltro_db_eager_fallback_total{reason="not-compilable"}` — see [Database metrics](/docs/observability/overview).
+
+### Same transaction guarantees as the shared schema
+
+Writes and explicit `transactional()` blocks run inside a transaction, and it is worth stating explicitly what that transaction gives you — it is **exactly** what a shared-schema transaction gives you, with no exceptions:
+
+- a typed error thrown inside it arrives typed (`_tag`, payload, prototype intact), so a mutation's declared `error:` union matches;
+- a transient conflict (serialization failure / deadlock, including one raised at COMMIT) is retried with backoff;
+- the caller's write attribution (`traceId` / `subjectId` / `procedure`) is carried onto every ChangeEvent the transaction produces.
+
+There is one transaction bracket behind both topologies, so there is no "namespace mode is a bit different" caveat to remember. See [Transactions](/docs/database/transactions).
 
 ### Fail closed on a missing tenant
 
@@ -174,6 +245,7 @@ export const notes = table('notes', {
 2. **An auto-index** on `tenantId` (`indexes: [{ fields: ['tenantId'] }]`). The name is auto-generated as `<tableName>_tenantId_idx`.
 3. **Read scoping** — the runtime AND-merges `WHERE tenantId = ctx.subject.tenantId` into every subscription against this table.
 4. **Insert auto-fill** — when an insert's row payload omits `tenantId`, the runtime stamps it from the request subject.
+5. **Write scoping** — `updateMany` / `deleteMany` and the fluent `update(t).where(...)` / `delete(t).where(...)` builders get the same predicate AND-merged onto their `WHERE`, and a **keyed-by-id** write (`update(t, id, patch)`, `delete(t, id)`, `hardDelete`, `patchJson`) resolves its target row inside the caller's tenant before writing — see [What it does NOT do](#what-it-does-not-do).
 
 The mixin's stable id is `voltro/tenant`. The execution lives in the runtime's `wrapStoreWithMixinBehaviour` (write side) and the CLI's `applyTenantScope` (read side) — both key off that id. The mixin source is `voltro/packages/plugin-multitenancy/src/mixin.ts`.
 
@@ -214,9 +286,26 @@ If you DON'T pass `tenantId`, the runtime auto-fills it from `ctx.subject.tenant
 
 When you DO pass an explicit `tenantId` (an admin writing into another tenant), the framework does NOT silently substitute the subject's value — silent substitution is a footgun. Guard the write with `assertOwnTenant` (see below); a genuine cross-tenant write runs as the `system` subject via `runAsSystem` (see [Edge cases](/docs/multi-tenancy/edge-cases)).
 
+## Keyed writes resolve inside your tenant
+
+`ctx.store.update(table, id, patch)`, `delete(table, id)`, `hardDelete(table, id)` and `patchJson(table, id, ...)` address a row by primary key. On a `tenant()` table the runtime resolves that key **inside `subject.tenantId`** before writing, so an id that came straight from request input cannot reach another tenant's row:
+
+```ts
+export default async (input, ctx) => {
+  // input.id is client-supplied. Another tenant's id → TenantRowNotFound.
+  return ctx.store.update('notes', input.id, { title: input.title })
+}
+```
+
+When the row is not in your tenant the call **fails** with `TenantRowNotFound` (`@voltro/runtime`) rather than returning `null` / `false`. Declare it in the descriptor's `error:` to surface it typed at the client.
+
+The error is raised **identically** whether the row is missing or belongs to another tenant, and carries nothing that separates them — reporting the two differently would let a caller probe for row ids in other tenants. Do not try to recover the distinction; there is nothing on the wire to recover it from, on purpose.
+
+Not affected: subjects with no tenant at all — a schedule firing, a resumed workflow, a `*.subscribe.ts` handler — still span tenants by design, and so does a write through the raw store.
+
 ## What it does NOT do
 
-- **Auto-guard writes.** Read scoping is automatic; mutations receive user-supplied input including `tenantId`. A client authenticated as tenant A can post `tenantId: 'B'` and the row lands in B without a guard. Call `assertOwnTenant` at the top of the executor:
+- **Decide which tenant an insert claims.** An insert that omits `tenantId` is stamped from the subject, but one that *sets* it is not silently substituted — a legitimate cross-tenant write exists. `assertOwnTenant` is the early, typed check for a handler that means to USE a claimed `input.tenantId`:
 
   ```ts
   import { assertOwnTenant, TenantMismatch } from '@voltro/plugin-multitenancy'
@@ -227,7 +316,7 @@ When you DO pass an explicit `tenantId` (an admin writing into another tenant),
   }
   ```
 
-  Declare `error: TenantMismatch` on the mutation descriptor so the rpc layer surfaces the rejection typed.
+  Declare `error: TenantMismatch` on the mutation descriptor so the rpc layer surfaces the rejection typed. It checks a *claimed* `tenantId` — a mutation whose input carries none never reaches it, which is why it is no longer what stands between you and a cross-tenant write.
 
 - **Apply to raw SQL.** A hand-written `@effect/sql` query bypasses the mixin. Write the filter yourself.
 
@@ -582,43 +671,100 @@ tenant's data.
 > `TenantResidencyUnresolved`. Home region not served here → typed
 > `TenantRegionUnavailable`. Both fail closed; that's the whole point.
 
-## Configure it
+## Declare it
+
+Residency is declared in `app.config.ts` and wired by both boot paths — `voltro
+dev` and `voltro serve` open one store per servable region and route every
+request through it. There is nothing to call from your own code.
 
 ```ts
-import { setResidencyConfig } from '@voltro/database'
-
-setResidencyConfig({
-  // tenant → home region (+ optional named connection for the home DB).
-  homes: [
-    { tenantId: 'acme',  region: 'eu-west' },
-    { tenantId: 'globex', region: 'us-east' },
-  ],
-  // The regions THIS deployment can actually serve (it holds their stores).
-  servableRegions: ['us-east'],
+export default defineApiApp({
+  tenancy: {
+    isolation: 'namespace',
+    residency: {
+      // The regions THIS deployment holds stores for.
+      servableRegions: ['eu-west'],
+      // region → the NAME of the env var holding that region's database URL.
+      regionUrlEnv: { 'eu-west': 'DB_URL_EU', 'us-east': 'DB_URL_US' },
+      // tenant → home region. An array, or a function resolving one at boot.
+      homes: [
+        { tenantId: 'acme', region: 'eu-west' },
+        { tenantId: 'globex', region: 'us-east' },
+      ],
+    },
+  },
 })
 ```
 
-A tenant mapped to two different regions is rejected at config time (ambiguous
-routing), and `servableRegions` must be non-empty.
+`regionUrlEnv` takes a variable NAME, not a URL: a connection string is a
+secret and `app.config.ts` is committed. Everything else about a region's store
+— pool bounds, TLS, `search_path`, statement timeouts — is inherited from the
+primary connection, so a region cannot silently run with different limits than
+the deployment it belongs to.
+
+`homes` may be a function (`() => Promise<TenantHome[]>`) if the mapping lives
+in your own table or control plane. It is resolved **once, at boot**: adding a
+tenant home needs a restart. That is deliberate — the alternative is a cache
+with a staleness window on a decision whose entire value is that it is never
+wrong.
 
-## Resolve + bind per request
+### It requires namespace isolation, and refuses to boot without it
 
-`bindResidentStore` picks the store for the subject's home region from the
-per-region handles this deployment holds — failing closed if the home is
-unresolved or not served here:
+`residency` without `isolation: 'namespace'` is a **boot refusal**, not a
+warning. The region keeps regions apart; the namespace keeps tenants apart
+inside a region. With only the first, every tenant in a region would share one
+set of tables — the region boundary held and the tenant boundary dropped, which
+looks like residency and is not.
+
+The other boot refusals, all for the same reason (a deployment that looks like
+it enforces residency and does not is worse than one that will not start):
+
+- a servable region with no `regionUrlEnv` entry;
+- a servable region whose env var is unset;
+- an empty `servableRegions`;
+- a tenant mapped to two different regions.
+
+## What a request gets
+
+Every request resolves its subject's tenant → home region → **that region's
+store**, and only then binds the tenant's namespace inside it. Residency picks
+which database; the namespace picks which tenant's tables in it.
+
+Three refusals, none of which falls back:
+
+| Situation | Result |
+|---|---|
+| Subject has no resolvable tenant | `TenantResidencyUnresolved` |
+| Tenant has no home mapped | `TenantResidencyUnresolved` |
+| Tenant homed in a region this deployment does not serve | `TenantRegionUnavailable`, naming the region so a gateway can route it |
+
+`ctx.storeForTenant(id)` resolves residency for **that** tenant, not the
+caller's — so a handler acting on another tenant either reaches that tenant's
+region or is refused. It is the seam background work must use: a schedule or a
+workflow runs with no request and, under the system subject, no tenant, so
+`ctx.store` on those paths is the primary store. A job that touches one tenant's
+rows has to say which tenant, and `storeForTenant` is how it says so.
+
+A transaction is never re-routed. When a mutation hands its transaction-scoped
+store to a nested call, that store is used as given — it already went through
+residency to exist, and moving writes off the connection holding the lock would
+be a worse failure than the one residency prevents.
+
+## Driving it yourself
+
+The resolvers are exported for a control plane that owns the mapping itself —
+`setResidencyConfig`, `residentPlacement`, `bindResidentStore`. The declaration
+above calls the first two for you; reach for them directly only if you are
+building the region topology outside the framework.
 
 ```ts
 import { bindResidentStore } from '@voltro/database'
 
-// stores: ReadonlyMap<region, StoreHandle> — what THIS deployment wired.
+// stores: ReadonlyMap<region, StoreHandle>
 const { store, placement } = bindResidentStore(subject, config, stores)
 // placement = { region, namespace, connectionKey? }
-// throws TenantRegionUnavailable for an EU-homed tenant on a US deployment.
 ```
 
-`residentPlacement(subject, config)` gives the placement alone (region +
-the tenant's namespace within that region's store) without needing the handles.
-
 ## Provision a new resident tenant
 
 `provisionResidentTenant` runs an injected provisioner against the tenant's HOME

package/templates/agent-docs/observability.md

@@ -71,7 +71,7 @@ Even with no exporter, `voltro dev` installs a **buffer-only** tracer — that's
 
 ## Metrics export
 
-Separate from tracing, the framework records **metrics** into Effect's global `MetricRegistry` — one source of truth (`voltro_rpc_*`, `voltro_http_*`, `voltro_plugin_hook_*`, `voltro_subscription_*` + `voltro_subscriptions_active`, plus `effect_fiber_*` and any custom metric). Three ways to get them out:
+Separate from tracing, the framework records **metrics** into Effect's global `MetricRegistry` — one source of truth (`voltro_rpc_*`, `voltro_http_*`, `voltro_plugin_hook_*`, `voltro_subscription_*` + `voltro_subscriptions_active`, `voltro_db_*`, plus `effect_fiber_*` and any custom metric). Three ways to get them out:
 
 ```bash
 # OTLP metrics — the SAME OTEL endpoint that enables trace export also enables
@@ -94,6 +94,55 @@ Two pull/push consumers read the SAME registry, so they can't disagree:
 - **[`@voltro/plugin-datadog`](/docs/plugins/datadog)** — agentless push to Datadog's `/api/v2/series` (for setups without an Agent / OTLP collector). With an Agent, prefer pointing `OTEL_EXPORTER_OTLP_ENDPOINT` at it instead.
 - The dashboard **Metrics** panel reads the same snapshot via `GET /_voltro/inspect/metrics`.
 
+## Database metrics (`voltro_db_*`)
+
+Every dialect store emits the same five series, so a dashboard built against one
+database keeps working after a migration to another. The labels are `dialect`
+(`postgres` · `mysql` · `mariadb` · `mssql` · `sqlite` · `turso`) and `op`
+(`select` · `insert` · `update` · `delete` · `upsert` · `raw` · `transaction`
+· `ddl`).
+
+| Series | Type | What it answers |
+| --- | --- | --- |
+| `voltro_db_queries_total` | counter | Query rate, split by operation kind. |
+| `voltro_db_query_duration_seconds` | histogram | p50/p95/p99 per operation — `histogram_quantile` over the buckets. |
+| `voltro_db_errors_total` | counter | Statement failure rate. |
+| `voltro_db_operations_in_flight` | gauge | Concurrency the framework is holding right now. |
+| `voltro_db_eager_fallback_total` | counter | Eager loads that dropped off the single-roundtrip fast path. |
+
+**No table name is ever a label.** Table names grow with your schema, and a
+label that grows with the schema is how a scrape target falls over. The table
+appears in the log line instead.
+
+**`voltro_db_operations_in_flight` is not the driver's pool queue.** It counts
+operations the framework currently has in flight, which is an upper bound on the
+connections it holds — the same number on every dialect. Your driver's own
+`waiting` count is not exposed. In practice you alert on this gauge sitting near
+your pool size *together with* the duration histogram's tail growing: a starved
+pool shows up as acquire time inside the query timing.
+
+### `voltro_db_eager_fallback_total` — the one to alert on
+
+An `eager:` query normally compiles to **one** round trip (a JSON aggregate).
+When it can't, the framework silently uses the portable multi-query walker
+instead — correct, and one round trip per relation level, on every call. That is
+a permanent per-query cliff with no error attached to it, which is why it is
+counted. The `reason` label separates the two very different cases:
+
+- `not-compilable` — the query shape can never take the fast path (an
+  unregistered relation, an ambiguous inferred foreign key, or an eager read
+  under physical tenant isolation). Steady state. Worth knowing about, not worth
+  paging on.
+- `execute-failed` — the fast path compiled, **ran, and threw**, so the query
+  paid for both paths. This is the one to alert on. It usually means a database
+  or driver upgrade changed something under the JSON-aggregate query.
+
+Both also log: a `warn` the first time a given table and reason are seen, then
+again at most every 5 minutes while it persists (`VOLTRO_DB_EAGER_FALLBACK_WARN_INTERVAL_MS`,
+`0` = once only). The counter is never rate-limited — the log line answers "is
+this happening now", the counter answers "has this been happening since the
+deploy three weeks ago".
+
 ## Routing traces to a vendor
 
 The env-driven OTLP path above ships traces to any OTLP/HTTP collector. For **deep, opt-in vendor integration** — install one plugin, get traces + errors + logs all correlated by the same `traceId`, zero `OTEL_*` env — a plugin can contribute to the framework's tracer directly via `contributeObservability`:
@@ -122,7 +171,11 @@ Inside a mutation / action / workflow executor, just use Effect:
 ```typescript
 import { Effect } from 'effect'
 
-export const myAction = defineAction({ ... })
+export const myAction = defineAction({
+  name: 'reports.rebuild',
+  guards: [{ scope: 'reports:write' }],
+  /* input, output */
+})
 
 export default (input, ctx) =>
   Effect.gen(function* () {
@@ -172,7 +225,9 @@ client.mutation.placeOrder        traceId=4bf92f35…
 The in-memory ring always keeps EVERY span for live debugging. SEPARATELY, on postgres, the framework can durably mirror a SUBSET of spans into `_voltro_traces` so the in-app Traces dashboard survives restarts. This is a **dev convenience** — at real volume durable tracing belongs in an **OTLP backend (Tempo / Honeycomb / Datadog), not your OLTP postgres** (set `OTEL_EXPORTER_OTLP_ENDPOINT`). A row-per-span firehose into postgres is what turned this table into ~85% of a production DB. So persistence is **environment-aware + fully configurable**:
 
 - **Default OFF in production, `interesting` in dev.** `voltro dev` (not `NODE_ENV=production`) persists only "interesting" spans. `voltro serve` / `voltro start` default `NODE_ENV=production` when it's unset, so they persist NOTHING and **`_voltro_traces` is not even created** — use OTLP in prod. An explicit `NODE_ENV` is never overridden.
-- **`VOLTRO_TRACING_PERSIST`** = `off` | `errors` | `interesting` | `all` (overrides the env default everywhere). `interesting` = error + slow + per-trace root spans, MINUS the high-volume subscription delivery (snapshot/delta) spans. `errors` = error spans only. `all` = every non-delivery span. `off` = no persistence and no table.
+- **`VOLTRO_TRACING_PERSIST`** = `off` | `errors` | `interesting` | `all` (overrides the env default everywhere). `interesting` = error + slow + per-trace root spans, MINUS the high-volume subscription delivery (snapshot/delta) spans, MINUS the framework's own background-task reads. `errors` = error spans only. `all` = every non-delivery span. `off` = no persistence and no table.
+
+  **Why background tasks are excluded from "slow".** The framework polls four of its own tables on a timer (`_voltro_schedule_claims`, `_voltro_workflow_pending`, `_voltro_workflow_pauses`, `_voltro_ai_inferences`). Those reads are slow exactly when the database is under pressure — which is when persisting them costs the most. A consumer measured the loop closing on itself: `_voltro_traces` at 476 571 rows / 335 MB, writing ~11 INSERTs/s onto the same 15-slot pooler the app read through, 99 % of it framework poller spans. Pool pressure makes the spans slow, slow spans are "interesting", persisting them costs pool. They are still kept when they ERROR, and `all` mode still keeps everything. A request-path framework table like `_voltro_api_keys` is NOT excluded — a slow lookup there is a real user waiting.
 - **`VOLTRO_TRACING_SLOW_MS`** (default `500`) — the "slow" threshold used by `interesting`.
 - **`VOLTRO_TRACING_PERSIST_DELIVERY`** (default off) — also persist the subscription delivery spans (the firehose; rarely wanted).
 - **`VOLTRO_TRACING_SAMPLE`** (`0`–`1`, default `1`) — per-*trace* sampling (a kept trace keeps all its eligible spans; errors are never sampled out). `=0` with no explicit mode means off.