[objectstack-fleet]

Requested by Bill · project thread

Fixes #25230
Part of #15212

Clause-②: no
Metadata-protocol: none

What changes

Diagnostics only. No write changes: no statement, scope, row or refusal moves. The [tenant-audit] prefix and text are byte-identical.

1. driver-sql: an insert whose rows carry their organization is not audited. SqlDriver.auditMissingTenant takes the inserted rows from the two insert doors (create, bulkCreate). When every row carries a non-empty tenant column (empty is spelled as injectTenantOnInsert spells it), the line is skipped: an insert is confined to the organizations its rows name. One row without the column keeps the line. update, delete, updateMany, deleteMany, bulkDelete and upsert with no tenantId still warn, whatever the payload says. For an update or delete the column is a value being written, not the scope, and an upsert's merge leg can reach another organization's row.
2. objectql: the engine declares the D8 wall-exemption to the driver. buildDriverOptions fills in bypassTenantAudit: true when the Layer 0 verdict that plugin-security recorded on the operation is none and the engine's own fallback asking of the same ladder (computeTenantLayer0Verdict with the exemption withheld, the scope an unrecorded operation already gets) would have walled it. This is plugin-security's own crossedByPlatformAdmin test, read from the recorded value. It is the existing option, so there is no DriverOptions widening and no new OperationContext member, and the driver reads no posture it did not read before. It is not filled in when no verdict was recorded (a by-id write, a system context, no security layer), under single, for an insert (write target), for an object outside the tenant machinery (tenancy-disabled, federated, no tenant field), for a verdict that does not parse, or when the caller supplied its own value.

Other drivers: Turso's local face and the SQLite WASM driver inherit SqlDriver.create / bulkCreate, so they get (1). Turso's remote face never called the audit. driver-memory and driver-mongodb have no tenant-audit warning.

Measured: a walled os serve boot, before and after

Setup (as on #25210's R4): pnpm dev -- --fresh on the showcase with OS_TENANCY_POSTURE=isolated, a 32-byte OS_SECRET_KEY, OS_AUTH_MEMBERSHIP_POLICY=invite-only and OS_PLATFORM_OWNER_EMAIL. @objectstack/organizations was declared in the showcase's package.json and linked for the run only; both were reverted and are not in this diff. Health 200 both times; 20 s settle after health; seeded admin sign-up included.

[tenant-audit] lines	base 0f1eeeeeb	this branch
create	16 (2 showcase_*, 14 sys_*)	0
bulkCreate	16 (all showcase_*)	0
update	5	5
updateMany	18	18
total	55	23

Every insert line is gone; every update and updateMany line stays, as the card requires.

Tests

• sql-driver-tenant-audit-insert-carries-tenant.test.ts (new, real SqlDriver on in-memory SQLite, 11 tests). Pins: create and bulkCreate whose rows carry the organization print nothing. Controls: a row without it, an empty organization, one row of a batch without it, and the byte-identical prefix all still warn; update (payload naming an organization), delete, updateMany, deleteMany and upsert (row naming an organization) all still warn.
• engine-tenant-audit-wall-exemption.test.ts (new, the DriverOptions seam and harness of engine-driver-read-scope.test.ts, 10 tests). Declared: recorded none under isolated on updateMany and deleteMany, and under group. Not declared: a walled verdict, no recorded verdict, single, an insert, a tenancy-disabled object, an unparseable verdict, a caller's own bypassTenantAudit: false.
• Two existing driver pins used a create whose row carried organization_id as the "write without tenant" shape: sql-driver-tenant-audit-posture.test.ts now uses a delete for that helper (and its bypassTenantAudit case), and sql-driver-tenant-scope.test.ts's throttle pin now uses two deletes. Their assertions are unchanged.
• Package suites: @objectstack/objectql test 464 files, 8686 passed; typecheck exit 0. @objectstack/driver-sql typecheck exit 0; test 3773 passed, 1 failed on the first run (the throttle pin above, which encoded the old insert behaviour), and the fixed file passes 61/61 with its two sibling audit files. Cross-package readers of the prefix: service-messaging delivery-claim-tenant-audit and delivery-update-tenant-audit integration tests 13/13; service-storage tenant-audit-update-delete-half-repairs 30/30.

Ablation

Both run through scripts/ablation-replace.mjs with the fix committed, and each restore was verified (blob equals HEAD, git diff HEAD empty). The tests import source, so no build leg is needed.

• Deleted the row-carries-tenant skip in auditMissingTenant: the 2 insert pins go red and the 9 controls stay green (2 failed, 9 passed).
• Removed the engine's opts.bypassTenantAudit = true for the exemption: the 3 "declared" pins go red and the 7 "not declared" stay green (3 failed, 7 passed). My first attempt was refused by the tool before running anything, because the replacement text was a substring of the anchor. The second attempt used a distinct replacement.

Gates

Run on the final head d323330402. node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derives 74 commands over 8 changed paths. I ran each one and captured its exit code before any pipe: 74/74 exit 0. --ran reports "74 derived famil(ies) accounted for — 74 run, 0 NOT-MEASURED". Two shallow-clone prerequisites were met first, by fetching 621a48760 (check-plugin-teardown-shape --self-test) and running --shallow-since=2026-07-17 (check-engine-split-ratio --days 90). On the earlier head b57e83d5, the same 72 were green and those two exited 3 and 2 on the shallow clone. CI runs everything else; this PR does not touch a governed surface.

Acceptance notes

• The 23 lines left at a walled boot are seed-time update and updateMany on showcase_* objects with no tenantId. That is the case the line exists for, and the card keeps it. Whether the showcase seed path should run those writes in an organization's context is outside this card. I'm noting it here and not filing it, since nothing is shown wrong.
• An exempt admin's by-id write records no verdict, so the engine scopes it by its own facts (the active organization), and nothing is declared. Only predicate writes carry the recorded none. This is ADR-0131 D8 as written; this PR does not move it.
• I did not exercise the exemption end to end through REST. It is pinned at the DriverOptions seam, where plugin-security's recorded verdict meets the engine. Boundary: NOT MEASURED: live exempt-admin predicate write.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 2 package(s): @objectstack/driver-sql, @objectstack/objectql, touching 8 documentable anchor(s).

10 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/data-modeling/drivers.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/data-modeling/index.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/data-modeling/queries.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/permissions/system-context.mdx (via buildDriverOptions (symbol, a method of class ObjectQL))
• content/docs/permissions/tenant-audit-census.mdx (via SqlDriver (symbol, a top-level class), auditMissingTenant (symbol, a method of class SqlDriver), buildDriverOptions (symbol, a method of class ObjectQL), bulkCreate (symbol, a method of class SqlDriver), bulkCreate (literal, a string literal in bulkCreate))
• content/docs/plugins/packages.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/protocol/kernel/index.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/protocol/kernel/lifecycle.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/protocol/objectql/query-syntax.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/protocol/objectql/types.mdx (via SqlDriver (symbol, a top-level class))

⛔ 3 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/v17/17-0.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/releases/v17/17-5.mdx (via SqlDriver (symbol, a top-level class))
• content/docs/releases/v17/17-6.mdx (via SqlDriver (symbol, a top-level class), bulkCreate (symbol, a method of class SqlDriver), bulkCreate (literal, a string literal in bulkCreate))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• 1 anchor(s) matched too much of the corpus to be a work list: ObjectQL (symbol, 72 pages)
• 1 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 24 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 1eb1afae071530f66f4d93d416e7f452ceab3de3 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from e5150730fb8d51cc44a0dfab3026cba84403a8fe — the merge of head 1313821b578acc2702e364c74aac8c7b1400b4b5 into base 1eb1afae071530f66f4d93d416e7f452ceab3de3, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin e5150730fb8d51cc44a0dfab3026cba84403a8fe && git checkout e5150730fb8d51cc44a0dfab3026cba84403a8fe
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 1eb1afae071530f66f4d93d416e7f452ceab3de3 1313821b578acc2702e364c74aac8c7b1400b4b5 && git checkout -B drift-repro 1eb1afae071530f66f4d93d416e7f452ceab3de3 && git merge --no-ff 1313821b578acc2702e364c74aac8c7b1400b4b5

node scripts/docs-audit/affected-docs.mjs --json 1eb1afae071530f66f4d93d416e7f452ceab3de3

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs 1eb1afae071530f66f4d93d416e7f452ceab3de3 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: TIER_DEFAULT
Head-sha: 0d69599888e0aafb25db1911143f17372fb6d1bf
Local-runs: none

Reviewed at 2026-10-22T19:35Z. Inputs: card #25230 (body, claim 6347729103, dev report 6349387651), record 6341425088 on #25210 (③ item 3 only), this PR's body, file list and net diff against its merge base 0f1eeeeeb, and the check-runs on the head. Read from git and the REST API only. Nothing was built, run or re-run.

The head moved after the dev report. The report and the review brief both name d323330402. The PR head is 0d69599888, a ninth file pushed at 2026-10-22T19:27Z by the same dev session: content/docs/permissions/tenant-audit-census.mdx, +17/−9. This record reviews 0d69599888. Its code is byte-identical to d323330402; the only change is the docs page.

① Derived judgments

1. Diagnostics only, no write behaviour change: RIGHT.

   • Where the exemption is decided. It is decided once, in buildDriverOptions, as wallExempt = tenantObject && isTenantAuditInScope && !scope.writeTarget && wallExemptedOperation(execCtx, scope.recordedVerdict). wallExemptedOperation returns true only when two things hold. First, the recorded verdict parses as TenantLayer0VerdictSchema with kind: 'none'. Second, engineLayer0Verdict (the engine's existing fallback, now extracted with the same inputs: objectHasOrgIdField: undefined, posturePermitsCrossTenant: false, isPlatformAdmin: false) does not answer none.
   • The extraction does not change the fallback. driverReadScope calls the extracted helper with the same arguments the inline call had, so read and write scope are unchanged.
   • Every reader of bypassTenantAudit. A git grep over non-test source in packages/** finds one driver reader: sql-driver.ts:16108, an early return inside auditMissingTenant, before the warn. It changes no filter, no stamp and no refusal.
     • driver-turso and driver-sqlite-wasm inherit that method.
     • driver-memory and driver-mongodb have no reader and no audit.
     • Every other hit is a writer: the engine itself, service-settings, service-messaging, service-datasource. Or it is the pass-through key list at engine.ts:607.
   • No new OperationContext member and no DriverOptions key. The diff touches no interface. The driver adds no posture read; isMultiTenantMode() was already there.
   • The changed early return. It now also skips returning base when wallExempt is true. The only effect is a shallow copy of base that carries bypassTenantAudit: true. That is the same copy every other branch already makes.
   • Traced: cases where the flag is not set.
     • A tenant user under a wall. The recorded verdict is organization, organizations or deny, so the answer is false.
     • An isSystem write. plugin-security's middleware returns next() for context.isSystem (security-plugin.ts:2561) before step 3 records anything, so the recorded verdict is undefined and the answer is false. The D13 cut is untouched. An out-of-scope object is still muted by the existing branch, and an in-scope one still warns.
     • A federated or tenancy-disabled object. tenantObject is false.
     • An insert. It is built with { writeTarget: true } (engine.ts:17276).
     • A by-id write and the cascade delete (engine.ts:21730). Neither passes a recorded verdict.
     • A delegated write. intersectTenantLayer0Verdicts of the admin's none with the delegator's wall is a wall.
     • The Layer 0: should a verified platform admin cross the org wall by PERMISSION entitlement, not only posturePermitsCrossTenant's three shapes? (cloud#1676 upstream half) #12974 owner bypass. It records none on reads only. There the flag is inert, because the driver reads it only in the write-op audit.
     • Posture. The posture provider the engine reads is the one plugin-security hands it, so whenever a verdict was recorded, the two sides ask the same posture.

2. driver-sql insert skip: RIGHT.

   • The two insert doors. create passes [toInsert] before injectTenantOnInsert. bulkCreate moves its audit call after the id-assignment map and before injection, and passes every row.
   • The skip condition. The skip needs insertRows.length > 0 && insertRows.every(carriesTenant), so one row without the column keeps the line. An empty bulkCreate keeps the line too, as before.
   • What counts as carrying. "Carries" means not undefined, not null and not ''. That is the exact spelling injectTenantOnInsert uses, so a row with organization_id: null still warns. A non-object row counts as not carrying.
   • Other ops are unchanged. update (9061), upsert (9753), delete (10114), bulkDelete (10383), updateMany (10442) and deleteMany (10483) pass no rows, so they warn as before.
   • The line is unchanged. The warn string and its meta object are not in the diff, so the [tenant-audit] OP on tenant-scoped object "OBJECT" without options.tenantId prefix is byte-identical. That keeps service-messaging's delivery-claim-tenant-audit.integration.test.ts:64 and delivery-update-tenant-audit.integration.test.ts:97 matching.

3. Tests: RIGHT. One fixture move, one swap that strengthens a test, no assertion weakened.

   • sql-driver-tenant-audit-posture.test.ts.
     • writeWithoutTenant was a create whose row carried organization_id. It is now a by-id delete. Every true and false expectation is unchanged; the first one's meta now names op: 'delete'.
     • The bypassTenantAudit case moved from a create to a delete. On the old shape that case would have passed with or without the bypass at this head, so the move strengthens it.
     • The updateMany text test only re-seeds its row with a direct create.
   • sql-driver-tenant-scope.test.ts. The throttle pin swaps two creates for two deletes. The assertion is unchanged: one warn per object:op.
   • Do the new pins go red without the fix?
     • In the driver file, the create and bulkCreate "no line" pins depend only on the new every(carriesTenant) return. Delete it and both print a line, so both go red; the 9 controls do not depend on it.
     • In the engine file, the three "declared" pins assert bypassTenantAudit === true on a recorded none, and nothing else in buildDriverOptions sets it for a non-system context on a tenant object. Remove the assignment and all three go red; the 7 "not declared" pins stay green.
     • That reasoning matches both ablations the dev reports (2/9 and 3/7).

4. Measurement: PLAUSIBLE against the code.

   • The insert lines. At a walled seed boot the inserts are system context, refused above the driver when they carry no organization (D9), so each one that reaches the driver carries organization_id. That fits 32 → 0 for create and bulkCreate.
   • The update lines. The 5 update and 18 updateMany lines are isSystem seed writes. They record no verdict, so they get no exemption and still warn, as the card requires.
   • The counts. The throttle is per object:op, so the counts are distinct object/op pairs, not write totals.
   • Nothing still warns that the Acceptance says should not. The exemption half is pinned at the DriverOptions seam only. The PR body states NOT MEASURED: live exempt-admin predicate write, which the card's Acceptance does not require.

5. The docs commit (tenant-audit-census.mdx): the sentences are RIGHT; the commit is the conflict below.

   • Checked sentence by sentence, the new guard list is true of this head: the D13 isSystem cut, the D8 exemption fill-in, guard 6 for insert rows, and "thread an elevated one and an object with a tenant column is still audited, unless…".
   • It answers the docs-drift comment and the stale lines 49-50 that record 6341425088 ③2 named.
   • It is not in the dev report's files_changed (8 files), and the report's 74/74 gate run was taken on d323330402, not on this file.

② Semver level

RIGHT.

• Two patch changesets: @objectstack/driver-sql and @objectstack/objectql. Both packages are published (private unset, 18.0.0).
• Clause-②: no and Metadata-protocol: none are line-initial in the PR body and in both changeset bodies. No (narrowing) arm, and no BREAKING banner is owed.
• Clause-②: no holds. packages/spec is untouched, so DriverOptions, OperationContext and TenantLayer0VerdictSchema do not move. The only exported-class signature change is an optional trailing parameter on the protected SqlDriver.auditMissingTenant, which existing overrides and callers still satisfy. The new engine methods are private.
• Metadata-protocol: none holds: nothing an author can write moves.
• Check Changeset succeeded on d323330402, which carries the same two changesets. It has not run on this head (see FAIL item 1).

③ Boundary flags

FAIL item 1: the head conflicts with main, and no check-run exists on it.

• The conflict. main's 24360dcfb (fix(plugin-sharing): the declared-rule organization walk ends on the rows read; ADR-0131 small carriers retire the NULL-means-global texts #25266) rewrote bullet 2 of content/docs/permissions/tenant-audit-census.mdx (the isSystem mute is now schema-cut), and 0d69599888 rewrites the same lines. GitHub reports mergeable: false, mergeable_state: dirty.
• No CI. GET commits/0d69599888…/check-runs answers total_count: 0. CI on the head is unmeasurable.
• This PR caused it. d323330402 does not touch the file and merged cleanly; the conflict arrived with this PR's own last commit.
• Fix. Merge main. Resolve bullet 2 so it keeps main's D13 wording and adds this PR's D8 clause. Then let the full check set run on the new head and re-report the gates for it.
• What this record does not cover. The code judgments above do not change on that merge if it touches only the docs page. Even so, this record does not cover a new head.

Check-run tally at posting:

• Head 0d69599888: 0 runs.
• For reference, not counted: the superseded d323330402 has 39 runs — 24 success, 7 skipped, 8 in_progress (Test Core (1/6)–(6/6), Type Check · workspace, Type Check · consumer gates). Of the five required contexts there, Lint & Repo Gates, Build Core and Governed Surface Queue Guard succeeded; Test Core and the type-check lanes had not finished.

Dev deviations: both ACCEPTED.

• The attribution line links the card thread. The line is the platform's, and the card reference Fixes #25230 is the first content line. It sits beside no other open card's number, and Part of #15212 carries no closing keyword.
• The skipped MCP reviewer request: the order forbids MCP writes, and the assignee rode pr_create.

Observations, not blocking:

• (a) There is no dedicated organization_id: null pin. undefined (missing key) and '' are pinned, and null is correct by reading. A one-line control would make it explicit.
• (b) wallExemptedOperation is "recorded none where the engine's fallback walls". It is not the literal crossedByPlatformAdmin test, which also needs isPlatformAdmin. The two differ only where plugin-security's objectHasOrgIdField (it checks for organization_id) and the engine's resolveTenantFieldName (a declared tenancy.tenantField) disagree. An example is an object named in platformGlobalObjects that declares its own tenant field. On such an object the wall itself returned none and the effect is one silenced warning, so this is diagnostics only.
• (c) The PR body says "Fixes fix(objectql,driver-sql): ADR-0131 8c-1 follow-up — an elevated insert whose row carries its organization warns [tenant-audit] under a wall, and a wall-exempt admin write cannot declare the exemption to the driver #25230". Both of the card's Wanted items ship, so closing on merge is right.

Implemented-by: claude/project-thread-44gu3q
Reviewed-by: session_01FaVyM6YvQLg9CsjPVCYc5K

VERDICT: FAIL

[objectstack-fleet]

Contract review

Served-tier: TIER_DEFAULT
Head-sha: 652114639b022d083ecf335877e944e3e84369f1
Local-runs: none
Scope: content/docs/permissions/tenant-audit-census.mdx, packages/drivers/driver-sql/src/sql-driver-tenant-audit-insert-carries-tenant.test.ts + packages/objectql/src/engine.ts, packages/drivers/driver-sql/src/sql-driver.ts (byte-compared)

The seat's review of record on the head that answers the FAIL of 6349582997 (on 0d69599888). Inputs: that record, the dev's re-report 6350231223 on #25230, the two commits since 0d69599888 (merge b6a43d4758 of origin/main, test 652114639b), and the head's check-runs. Read from git and the REST API only.

① Derived judgments

1. The FAIL item is answered. main was merged in (no rebase); the PR reads mergeable: true. In tenant-audit-census.mdx the conflicting bullet 2 keeps main's D13 wording (the engine sets bypassTenantAudit on an isSystem write only where the object's schema puts it out of scope) and adds this PR's D8 clause (a predicate write the wall exempted: recorded verdict none where the wall would apply). Guard 6 and the rewritten closing paragraph state the insert skip as the code does it: create / bulkCreate only, every row carrying the field; updates, deletes and upserts audited whatever their payload says. True against sql-driver.ts at this head.
2. The code is the reviewed code. git diff 0d69599888...652114639b over packages/objectql/src/engine.ts and packages/drivers/driver-sql/src/sql-driver.ts is empty; the commits the merge brought from main touch neither package. Every code judgment of 6349582997 (① 1–5: diagnostics only, one decision site, one reader of bypassTenantAudit, the insert skip, unweakened tests) carries to this head.
3. The new control (create: a null organization is no organization — it still warns) pins the null case the previous record named as unpinned; it asserts the line is kept, so it goes red only if the skip ever treated null as carrying.

② Semver level

Unchanged: two patch changesets (@objectstack/driver-sql, @objectstack/objectql), Clause-②: no, Metadata-protocol: none; packages/spec untouched.

③ Boundary flags

• CI at this write: 32 success, 6 skipped, 3 in progress (Test Core (2/6), (3/6), (4/6)). Landing waits for every check on this head to read completed green.
• The dev re-reported the gates on this head (106/106 derived gates, full build 76/76, targeted tests 62/62 + 23/23) with the 9-file list.

Implemented-by: claude/project-thread-44gu3q
Reviewed-by: session_01FaVyM6YvQLg9CsjPVCYc5K

VERDICT: PASS

[objectstack-fleet]

席位核对

ACCEPT · domain:engine seat 2 (seat post #20966) · os-bill · session_01FaVyM6YvQLg9CsjPVCYc5K · 2026-10-22T20:11Z · head 652114639b022d083ecf335877e944e3e84369f1 · card #25230 (p3, Part of #15212).

1. Form: draft, Fixes #25230, Part of #15212, assignee os-bill, 9 files. check-governed-merges --pr 25274: not governed, under 3000 changed lines ⇒ ordinary queue landing.
2. Premise measured: the dev reports 6349387651 and 6350231223: a walled showcase boot printed 55 [tenant-audit] lines before and 23 after — inserts 32 → 0, update 5 and updateMany 18 kept; two ablations red as expected; 106/106 derived gates on this head.
3. Gates: the seat's review of record at TIER_DEFAULT: FAIL 6349582997 on 0d69599888 (a docs conflict with main, no CI on that head; the code judged right), then PASS 6350254884 on this head (main merged in, bullet 2 keeps main's D13 wording plus this PR's D8 clause, code byte-identical, a null control added). Landing waits for every check on this head to read completed green.
4. Accepted deviations:
   • The exemption is declared through the existing bypassTenantAudit option, decided once in buildDriverOptions (recorded verdict none where the engine's own fallback would wall): no DriverOptions widening, no new OperationContext member, Clause-②: no.
   • The docs page (content/docs/permissions/tenant-audit-census.mdx) joined the diff after the first report; it states the new guards truly.
   • The attribution line links the card thread; the reviewer request was skipped as the order said.
5. Out of scope, disposed: the engine's test (none where the fallback would wall) differs from plugin-security's crossedByPlatformAdmin only on an object declaring its own tenant field instead of organization_id, where the wall already answered none; the only effect is one silenced warning. Noted, not filed.
6. Landing: once every check on this head is green, the seat flips ready and arms auto-merge through the relay; the card closes on merge by Fixes #25230.

[objectstack-fleet]

Contract review

Served-tier: TIER_DEFAULT
Head-sha: 1313821b578acc2702e364c74aac8c7b1400b4b5
Local-runs: none
Scope: packages/drivers/driver-sqlite-wasm/src/sqlite-wasm-driver-tenant-scope.test.ts

The seat's review of record on the head that answers Test Core (3/6) red on 652114639b (check-run 120046342174: driver-sqlite-wasm's tests exited 1). One commit since that head; git diff 652114639b..1313821b5 touches this one test file and nothing else, so every judgment of 6350254884 and 6349582997 carries.

① Derived judgments

1. Root cause is this PR's, and the fix is the twin of a fix already reviewed. SqliteWasmDriver inherits SqlDriver.create and its audit. Its throttle pin ("logs once per object:op") drove the throttle with two creates whose rows carry organization_id; since this PR such an insert is not audited, so the pin saw 0 lines instead of 1. The same pin in driver-sql (sql-driver-tenant-scope.test.ts) was already moved to delete in the reviewed diff.
2. No assertion weakened. The pin still asserts exactly one warning for two same-object same-op writes (the throttle), now on op: 'delete', which is still audited. The comment states why a create cannot exercise it.
3. No third twin: driver-turso inherits the same implementation; the dev reports its suite green locally (2492 passed) and sqlite-wasm 704/704.

② Semver level

Unchanged: test-only; no changeset moves.

③ Boundary flags

• Landing waits for every check on this head to read completed green; the dev is re-running the derived gates on this head and re-reports on the card.

Implemented-by: claude/project-thread-44gu3q
Reviewed-by: session_01FaVyM6YvQLg9CsjPVCYc5K

VERDICT: PASS

[objectstack-fleet]

Landing note · domain:engine seat 2 (seat post #20966) · os-bill · session_01FaVyM6YvQLg9CsjPVCYc5K · 2026-10-22T20:51Z

Head 1313821b578acc2702e364c74aac8c7b1400b4b5 moved from the ACCEPT head (652114639b, ACCEPT 6350266730) by one test-only commit, the driver-sqlite-wasm throttle pin's twin of the driver-sql fix; the seat's review of record PASS 6350393123 names this head. Every check on it reads completed green (36 success, 6 skipped), mergeable_state: clean, check-governed-merges --pr 25274 not governed. The seat flips ready and arms auto-merge now.

---

Generated by Claude Code