test(driver-sqlite-wasm): open the tenant audit with the real posture knob, not the deleted memo (#5262)

Regression from this branch's own driver-sql change, caught by CI
(Test Core 2/3): `SqliteWasmDriver extends SqlDriver`, and this suite's
tenant-audit test switched multi-tenant mode on by poking the private
`_multiTenantMode` memo:

    (driver as any)._multiTenantMode = true;

That memo is gone — `isMultiTenantMode()` now resolves the tenancy posture
live — so the poke silently stopped doing anything, the gate read
single-org, no warning was emitted, and the assertion failed with
"expected [] to have a length of 1 but got +0". Reproduced locally against
the pre-fix test before changing it.

Fixed the way the sibling driver-sql suite already was: set the real
`OS_TENANCY_POSTURE=isolated` and restore it in a `finally`. This is
strictly better than what it replaces — the old poke reached into an
implementation detail, so it began lying the moment that detail changed,
which is exactly how it failed. Driving the documented knob cannot go
quietly stale that way.

Also strengthened the neighbouring `bypassTenantAudit` case in the same
block, which was VACUOUS: it never set a posture, so the audit returned at
the multi-tenant gate and `warnSpy` was empty regardless of the flag under
test — it would have passed with the flag deleted. (Vacuous before this
branch too; it simply never poked the memo the way its sibling did.) It now
sets the posture, so the flag is the only thing that can keep the log
quiet; verified by deleting the flag and watching it go red.

Repo-wide grep confirms no third package pokes `_multiTenantMode`; the only
remaining mentions are this branch's own comments and the tombstone
assertion in sql-driver-tenant-audit-posture.test.ts.

Full suites (not just the touched file): driver-sqlite-wasm 16 files /
232 tests passed; driver-sql 63 files (59 passed, 4 skipped) / 740 passed
+ 44 skipped. typecheck Done for both; eslint clean.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015W6nhsDrz6zWQc8je12a1t

Author: claude

packages/plugins/driver-sqlite-wasm/src/sqlite-wasm-driver-tenant-scope.test.ts

@@ -287,27 +287,58 @@ describe('SqliteWasmDriver tenant scope (organization_id)', () => {
       (driver as any).logger = { warn: (msg: string, meta: any) => warnSpy.push({ msg, meta }) };
       // The tenant-audit warning only fires in multi-tenant mode (single-tenant
       // stacks now always have an organization_id column but no isolation).
-      (driver as any)._multiTenantMode = true;
-      await driver.initObjects(objects);
-
-      await driver.create('account', { id: 'x1', organization_id: 'org_a', name: 'X1' });
-      await driver.create('account', { id: 'x2', organization_id: 'org_a', name: 'X2' });
-      // Second create on same object:op should NOT add another warn (throttle).
-      expect(warnSpy.filter(w => w.meta?.op === 'create')).toHaveLength(1);
+      //
+      // [#5262] Configured through the real knob rather than by poking the old
+      // `_multiTenantMode` memo, which no longer exists: `SqliteWasmDriver
+      // extends SqlDriver`, and that memo froze a process-level fact into a
+      // per-instance verdict, so the gate now resolves the tenancy posture live
+      // on every call. Setting the env exercises the same resolution a real
+      // deployment does — and unlike the old poke it cannot silently stop
+      // meaning anything, because a wrong posture makes the assertion fail
+      // rather than quietly disabling the branch under test. Restored in the
+      // `finally` below. Mirrors the same fix in driver-sql's suite.
+      const priorPosture = process.env.OS_TENANCY_POSTURE;
+      process.env.OS_TENANCY_POSTURE = 'isolated';
+      try {
+        await driver.initObjects(objects);
+
+        await driver.create('account', { id: 'x1', organization_id: 'org_a', name: 'X1' });
+        await driver.create('account', { id: 'x2', organization_id: 'org_a', name: 'X2' });
+        // Second create on same object:op should NOT add another warn (throttle).
+        expect(warnSpy.filter(w => w.meta?.op === 'create')).toHaveLength(1);
+      } finally {
+        if (priorPosture === undefined) delete process.env.OS_TENANCY_POSTURE;
+        else process.env.OS_TENANCY_POSTURE = priorPosture;
+      }
     });
 
     it('does not warn when bypassTenantAudit is set', async () => {
       await driver.disconnect();
       const warnSpy: any[] = [];
       driver = new SqliteWasmDriver({ filename: ':memory:' });
       (driver as any).logger = { warn: (msg: string, meta: any) => warnSpy.push({ msg, meta }) };
-      await driver.initObjects(objects);
-      await driver.create(
-        'account',
-        { id: 'x1', organization_id: 'org_a', name: 'X1' },
-        { bypassTenantAudit: true } as any,
-      );
-      expect(warnSpy).toHaveLength(0);
+      // [#5262] A walled posture is a PRECONDITION of this assertion, not
+      // decoration. Without it the audit returns at the multi-tenant gate and
+      // `warnSpy` is empty no matter what `bypassTenantAudit` does — the test
+      // passed while proving nothing about the flag it names. (That was equally
+      // true before this change, where the absent `_multiTenantMode` memo
+      // resolved to single-org; the sibling test above happened to poke the memo
+      // and this one never did.) With the posture set, the flag is the only
+      // thing that can keep the log quiet.
+      const priorPosture = process.env.OS_TENANCY_POSTURE;
+      process.env.OS_TENANCY_POSTURE = 'isolated';
+      try {
+        await driver.initObjects(objects);
+        await driver.create(
+          'account',
+          { id: 'x1', organization_id: 'org_a', name: 'X1' },
+          { bypassTenantAudit: true } as any,
+        );
+        expect(warnSpy).toHaveLength(0);
+      } finally {
+        if (priorPosture === undefined) delete process.env.OS_TENANCY_POSTURE;
+        else process.env.OS_TENANCY_POSTURE = priorPosture;
+      }
     });
   });
 });