test(objectql,verify,runtime): declare OS_REGISTRY_LOG=warn in each suite's own vitest harness (#14016)

* test(objectql,verify,runtime): declare OS_REGISTRY_LOG=warn in each suite's own vitest harness

Measured per suite on origin/main b1b7d60, one full run each:

  objectql  16,194 stdout lines · 4,744 [Registry] · 10,984 structured-logger
  verify     5,670 stdout lines · 2,323 [Registry] ·  3,113 structured-logger
  runtime    6,730 stdout lines · 1,155 [Registry] ·  4,760 structured-logger

Against the console-carried population each suite emits (the structured
logger writes to process.stdout directly and is a separate question),
[Registry] is 91.5% in objectql, 91.3% in verify and 59.0% in runtime.

OS_REGISTRY_LOG is @objectstack/objectql's own published seam for that
verbosity (SchemaRegistryOptions.logLevel / REGISTRY_LOG_LEVELS). The
engine's shipped default stays 'info', and no library code learns what a
test runner is: the request lives in each harness, declaratively.

Claude-Session: https://claude.ai/code/session_01F3jdziLbAPGeceVNmSox5L

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

* test(objectql): let registry-log-level.test.ts own the variable it is about

The package harness now declares OS_REGISTRY_LOG=warn for every worker, and
this file's subject IS that variable. Its `afterEach` already deleted the
var; the symmetric `beforeEach` was missing, so the FIRST case ran at 'warn'
under a name that says 'info' — and stayed green, because both of its
expectations are negative ("not called").

Measured rather than reasoned: with the premise assertion added and the
`beforeEach` withheld, the case fails with `expected 'warn' to be 'info'`.
Both "default level" cases now assert the level they run at, so a future
harness key cannot silently re-point them again.

Claude-Session: https://claude.ai/code/session_01F3jdziLbAPGeceVNmSox5L

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

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: zhuangjianguo

packages/objectql/src/registry-log-level.test.ts

@@ -18,7 +18,18 @@ import { SchemaRegistry, REGISTRY_LOG_LEVELS } from './registry';
 describe('SchemaRegistry log-level gating (#3420)', () => {
   const warn = vi.spyOn(console, 'warn').mockImplementation(() => {});
   const debug = vi.spyOn(console, 'debug').mockImplementation(() => {});
-  beforeEach(() => { warn.mockClear(); debug.mockClear(); });
+  // This file's SUBJECT is `OS_REGISTRY_LOG`, so it owns that variable rather
+  // than inheriting it. The package's vitest harness declares
+  // `OS_REGISTRY_LOG=warn` for every worker (#13517), and without this
+  // `beforeEach` the FIRST case below ran at `'warn'` under a name that says
+  // `info` — green, because both of its expectations are negative. Measured,
+  // not reasoned: the premise assertion in that case fails with
+  // `expected 'warn' to be 'info'` when this line is removed.
+  beforeEach(() => {
+    delete process.env.OS_REGISTRY_LOG;
+    warn.mockClear();
+    debug.mockClear();
+  });
   afterEach(() => { delete process.env.OS_REGISTRY_LOG; });
 
   const reRegisterSameOwner = (r: SchemaRegistry) => {
@@ -28,6 +39,10 @@ describe('SchemaRegistry log-level gating (#3420)', () => {
 
   it('at the default (info) level, re-registering an owned object is silent — no warn, no debug', () => {
     const r = new SchemaRegistry({ multiTenant: false });
+    // The case's NAME is a premise about the level, so assert it rather than
+    // assume it: both expectations below are negative, so a quieter level
+    // satisfies them while measuring something this file never claimed.
+    expect(r.logLevel).toBe('info');
     reRegisterSameOwner(r);
     expect(warn).not.toHaveBeenCalledWith(expect.stringContaining('Re-registering owned object'));
     expect(debug).not.toHaveBeenCalledWith(expect.stringContaining('Re-registering owned object'));
@@ -44,6 +59,7 @@ describe('SchemaRegistry log-level gating (#3420)', () => {
     const manifest = { id: 'com.test', name: 'Test', namespace: 'test', version: '1.0.0' } as any;
 
     const info = new SchemaRegistry({ multiTenant: false });
+    expect(info.logLevel).toBe('info');
     info.installPackage(manifest);
     info.installPackage(manifest); // same-package reload → "Overwriting package"
     expect(warn).not.toHaveBeenCalledWith(expect.stringContaining('Overwriting package'));

packages/objectql/vitest.config.ts

@@ -4,6 +4,42 @@
 // vitest's defaults, deliberately — a key added here re-specifies behaviour
 // for every test file in the package (packages/cli/vitest.config.ts's header
 // records the incident that taught that).
+//
+// ── #13517: this suite asks the SchemaRegistry for quiet, DECLARATIVELY ─────
+//
+// Measured on THIS suite (one full `pnpm --filter @objectstack/objectql test`,
+// `origin/main` b1b7d6088a): 16,194 lines on the run's stdout, 4,744 of them
+// `[Registry] …`. 10,984 of the rest are the structured logger's
+// `<ts> INFO …` lines, which do not go through `console` at all and are NOT
+// what this key reaches (#13986) — so against the console-carried population
+// this suite emits, `[Registry]` is 4,744 of 5,210 = 91.1%, and 3,869 of those
+// are the single `Registered object:` line, emitted once per registered object
+// per registry construction across the package's 250 test files.
+//
+// `OS_REGISTRY_LOG` is `@objectstack/objectql`'s OWN published seam for that
+// verbosity (`SchemaRegistryOptions.logLevel` / `REGISTRY_LOG_LEVELS`,
+// registry.ts) — at `warn` the registry's private `log()` returns before
+// writing. What it does NOT silence is the diagnostics: the ADR-0005
+// `[Registry] Collision` lines go through a bare `console.warn` that the level
+// never gates, so a real shadowing still speaks here — measured, not inferred:
+// `registry-collision-order.test.ts` passes identically on both sides, and it
+// sets `logLevel = 'silent'` per registry anyway.
+//
+// ⛔ Two things this deliberately is NOT. It does not move the engine's
+// SHIPPED default (still `'info'` at registry.ts:1265, unchanged for every
+// production reader), and it does not make library code sniff
+// `process.env.VITEST` — a library that behaves differently under a test
+// runner would make every log reading in tests a reading of something other
+// than production. The request lives HERE, in the harness, where the test
+// author can see it.
+//
+// ⚠️ One test file in THIS package reads the same env var as its subject:
+// `registry-log-level.test.ts` pins how `OS_REGISTRY_LOG` resolves. It now
+// deletes the var in `beforeEach` (it already did in `afterEach`) and asserts
+// the level its "default" cases actually run at, so the harness key below
+// cannot silently re-point that file's premise. Without those two lines the
+// file's first case stays GREEN while testing `'warn'` under a name that says
+// `info` — measured red before they were added.
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig({
@@ -15,5 +51,9 @@ export default defineConfig({
     // Mechanism + measured costs: examples/app-showcase/vitest.config.ts.
     // Enforced repo-wide by scripts/check-console-intercept-disarm.mjs.
     disableConsoleIntercept: true,
+    // #13517: quiet the registry's per-item registration chatter — the
+    // engine's own `OS_REGISTRY_LOG` seam, not a change to its shipped
+    // default. Header docblock carries the measurement and the rationale.
+    env: { OS_REGISTRY_LOG: 'warn' },
   },
 });

packages/runtime/vitest.config.ts

@@ -1,5 +1,38 @@
 // Copyright (c) 2025 ObjectStack. Licensed under the Apache-2.0 license.
 
+// ── #13517: this suite asks the SchemaRegistry for quiet, DECLARATIVELY ─────
+//
+// Measured on THIS suite (one full `pnpm --filter @objectstack/runtime test`,
+// `origin/main` b1b7d6088a): 6,730 lines on the run's stdout, 1,155 of them
+// `[Registry] …`. 4,760 of the rest are the structured logger's `<ts> INFO …`
+// lines, which do not go through `console` at all and are NOT what this key
+// reaches (#13986).
+//
+// ⚠️ Read the share honestly, because this suite is NOT the dogfood one.
+// Against the console-carried population (1,957 lines) `[Registry]` is 1,155 —
+// **59%**, the largest single family but a long way from dogfood's 94.9%. The
+// remaining ~800 are a mixed tail this key cannot reach: `[sql-driver] while
+// creating/syncing table …` column reports, `[HonoServerPlugin] Server
+// stopped`, `Paged read of … is NOT deterministic`, `[action-audit] …` and
+// `[Protocol] DB hydration skipped …`. So the declaration below is worth its
+// line here, and it is also not the whole story here — quieting the rest is a
+// different question about those specific call sites, not a log level.
+//
+// `OS_REGISTRY_LOG` is `@objectstack/objectql`'s OWN published seam for that
+// verbosity (`SchemaRegistryOptions.logLevel` / `REGISTRY_LOG_LEVELS`,
+// registry.ts) — at `warn` the registry's private `log()` returns before
+// writing. What it does NOT silence is the diagnostics: the ADR-0005
+// `[Registry] Collision` lines go through a bare `console.warn` that the level
+// never gates, so a real shadowing still speaks here.
+//
+// ⛔ Two things this deliberately is NOT. It does not move the engine's
+// SHIPPED default (still `'info'` at objectql's registry.ts:1265, unchanged
+// for every production reader), and it does not make library code sniff
+// `process.env.VITEST` — a library that behaves differently under a test
+// runner would make every log reading in tests a reading of something other
+// than production. The request lives HERE, in the harness, where the test
+// author can see it.
+
 import { defineConfig } from 'vitest/config';
 import path from 'node:path';
 
@@ -120,6 +153,11 @@ export default defineConfig({
     // Mechanism + measured costs: examples/app-showcase/vitest.config.ts.
     // Enforced repo-wide by scripts/check-console-intercept-disarm.mjs.
     disableConsoleIntercept: true,
+    // #13517: quiet the registry's per-item registration chatter — the
+    // engine's own `OS_REGISTRY_LOG` seam, not a change to its shipped
+    // default. Header docblock carries the measurement and the rationale,
+    // including the tail this key does NOT reach in this package.
+    env: { OS_REGISTRY_LOG: 'warn' },
     globals: true,
     environment: 'node',
     include: ['src/**/*.test.ts'],

packages/verify/vitest.config.ts

@@ -4,6 +4,31 @@
 // vitest's defaults, deliberately — a key added here re-specifies behaviour
 // for every test file in the package (packages/cli/vitest.config.ts's header
 // records the incident that taught that).
+//
+// ── #13517: this suite asks the SchemaRegistry for quiet, DECLARATIVELY ─────
+//
+// Measured on THIS suite (one full `pnpm --filter @objectstack/verify test`,
+// `origin/main` b1b7d6088a): 5,670 lines on the run's stdout, 2,323 of them
+// `[Registry] …`. 3,113 of the rest are the structured logger's `<ts> INFO …`
+// lines, which do not go through `console` at all and are NOT what this key
+// reaches (#13986) — so against the console-carried population this suite
+// emits, `[Registry]` is 2,323 of 2,557 = 90.8%. This package boots real app
+// stacks in its harness, so the count is per-boot registration chatter.
+//
+// `OS_REGISTRY_LOG` is `@objectstack/objectql`'s OWN published seam for that
+// verbosity (`SchemaRegistryOptions.logLevel` / `REGISTRY_LOG_LEVELS`,
+// registry.ts) — at `warn` the registry's private `log()` returns before
+// writing. What it does NOT silence is the diagnostics: the ADR-0005
+// `[Registry] Collision` lines go through a bare `console.warn` that the level
+// never gates, so a real shadowing still speaks here.
+//
+// ⛔ Two things this deliberately is NOT. It does not move the engine's
+// SHIPPED default (still `'info'` at objectql's registry.ts:1265, unchanged
+// for every production reader), and it does not make library code sniff
+// `process.env.VITEST` — a library that behaves differently under a test
+// runner would make every log reading in tests a reading of something other
+// than production. The request lives HERE, in the harness, where the test
+// author can see it.
 import { defineConfig } from 'vitest/config';
 
 export default defineConfig({
@@ -15,5 +40,9 @@ export default defineConfig({
     // Mechanism + measured costs: examples/app-showcase/vitest.config.ts.
     // Enforced repo-wide by scripts/check-console-intercept-disarm.mjs.
     disableConsoleIntercept: true,
+    // #13517: quiet the registry's per-item registration chatter — the
+    // engine's own `OS_REGISTRY_LOG` seam, not a change to its shipped
+    // default. Header docblock carries the measurement and the rationale.
+    env: { OS_REGISTRY_LOG: 'warn' },
   },
 });