@sequenceholdings/orm 2.1.0 → 2.2.0

package/README.md

@@ -16,7 +16,7 @@ branch on a namespace or product identity. See
 Install the CLI and SDK together:
 
 ```bash
-pnpm add -g @sequenceholdings/studio-cli@0.1.35 @sequenceholdings/orm@2.1.0
+pnpm add -g @sequenceholdings/studio-cli@0.3.0 @sequenceholdings/orm@2.1.1
 ```
 
 Create a namespace project:
@@ -46,6 +46,29 @@ canonical metadata, snapshots, documents, and migration statements.
 Commit generated outputs and migrations with the
 source that produced them.
 
+Owned `defineTable` contracts support named `checks` and referential actions
+on enforced `toOne` links or composite `foreignKeys`:
+
+```ts
+const reports = defineTable('reports', {
+  id: t.uuid().primaryKey(),
+  status: t.text().notNull(),
+}, {
+  checks: [{ name: 'reports_status_check', expression: "status IN ('draft', 'active')" }],
+})
+
+const runs = defineTable('runs', {
+  id: t.uuid().primaryKey(),
+  reportId: t.uuid().notNull(),
+}, {
+  links: { report: toOne(reports, { on: 'reportId', enforce: true, onDelete: 'cascade' }) },
+})
+```
+
+Check expressions use a validated subset of PostgreSQL predicates. See
+[database constraints](../../../docs/platform/orm-v2.md#database-integrity-constraints)
+for the supported operators, actions, migration behavior, and limitations.
+
 Use `apply --dry-run` to rehearse a migration against a disposable copy of the
 target environment's data. `apply --no-create` refuses to provision a missing
 namespace, which is useful for deployment checks.
@@ -115,3 +138,19 @@ This client rollout switch does not bypass server feature flags or authorization
 - `@sequenceholdings/orm/drizzle` — supported Drizzle helpers for views
 - `@sequenceholdings/orm/codegen` — GraphQL Code Generator preset used by a
   scaffolded namespace
+
+The `@sequenceholdings/orm/client` entry point contains the persisted-operation
+executor and error types without importing compiler, migration, Node builtins,
+or third-party runtime dependencies. It is safe to bundle into browser and
+function applications. The Managed Functions SDK bundles this entry point so
+deployed functions do not install ORM's authoring dependencies.
+
+Use `createArtifactOrmExecutor` from `@sequenceholdings/artifact-studio` inside
+an authenticated Artifact, and `createFunctionOrmExecutor` from
+`@sequenceholdings/managed-functions/orm` inside a Managed Function. Both accept
+the generated JSON manifest and preserve the caller's governed data access.
+For a function invocation with no human caller (a Lattice step), use
+`createFunctionServiceOrmExecutor`, which acts as the function's attached
+service account. The host adapters supply authentication; they do not grant namespace access or
+register operations. Do not extract CLI credentials or invent a browser token
+provider to wire a generated client.