fix(runtime,client): split the ledger guard along the package boundary — CI has no client dist in runtime's test task

Test Core failed on the first push: the conformance test imported the built
client (`../../client/dist/index.mjs`), assuming the dist exists whenever
tests run. Wrong assumption — turbo's per-package test tasks build only their
own dependency closure, and runtime deliberately has no edge to client (the
reverse edge exists, so adding one is a build cycle turbo rejects). In CI the
dist therefore never exists for runtime's suite.

The fix is structural, not a skip: each package now verifies its own half.

- runtime keeps the dispatcher directions (registry domain ↔ ledger, both
  ways) plus ledger hygiene and the gap ratchet — no client import at all.
- client gains `route-ledger-coverage.test.ts`, which instantiates the real
  ObjectStackClient and asserts every ledger-named method resolves to a
  function. The ledger is imported as a relative SOURCE file: it is pure data
  with zero imports, and it lives in runtime because that is where routes are
  declared.
- the now-unneeded @objectstack/core/logger vitest alias is reverted.

Skipping when the dist is missing was rejected: Test Core would never
exercise the client direction, and the guard's whole point is that this
failure mode cannot go quiet again.

Verified: phantom-method negative check bites in the new home; client suite
117 passed, runtime suite 653 passed; eslint clean.

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

Author: claude

.changeset/route-ledger-audit-guard.md

@@ -1,5 +1,6 @@
 ---
 "@objectstack/runtime": patch
+"@objectstack/client": patch
 ---
 
 Route ledger + conformance guard for the dispatcher↔client surface (#3563)
@@ -8,8 +9,10 @@ Route ledger + conformance guard for the dispatcher↔client surface (#3563)
 `@objectstack/client` has no way to express it — now has an inventory and a
 ratchet. `route-ledger.ts` records the audited disposition of every dispatcher
 route (sdk / gap / server-only / public / dynamic / mismatch);
-`route-ledger.conformance.test.ts` fails when a dispatcher domain lands with no
-ledger entry, when an entry claims a client method that doesn't exist, and when
-the audited gap count (27 at PR-1) grows. Findings and follow-up slicing live
+The guard is split along the package boundary (a runtime→client edge is a
+build cycle): runtime's `route-ledger.conformance.test.ts` fails when a
+dispatcher domain lands with no ledger entry and ratchets the audited gap
+count (27 at PR-1); client's `route-ledger-coverage.test.ts` fails when a
+ledger entry claims a client method that doesn't exist. Findings and follow-up slicing live
 in `docs/audits/2026-07-dispatcher-client-route-coverage.md`. No runtime
 behavior change.

packages/client/src/route-ledger-coverage.test.ts

@@ -0,0 +1,39 @@
+// Copyright (c) 2025 ObjectStack. Licensed under the Apache-2.0 license.
+
+/**
+ * Route-ledger ↔ client-surface conformance (#3563) — the client half of the
+ * guard whose dispatcher half lives in
+ * `packages/runtime/src/route-ledger.conformance.test.ts`.
+ *
+ * Every ledger entry that names a client method must resolve to a real
+ * function on an instantiated client — the ledger cannot claim coverage the
+ * SDK does not have. This is the direction #3528 shipped through: the ledger
+ * equivalent of the day would have said "resume → automation.resume" while no
+ * such method existed.
+ *
+ * The ledger is imported as a relative SOURCE file deliberately: it is pure
+ * data (no imports), and a client→runtime package edge for it would be
+ * backwards — runtime is where routes are declared, so the ledger lives there,
+ * and each package verifies its own half.
+ */
+
+import { describe, it, expect } from 'vitest';
+import { ObjectStackClient } from './index';
+import { ROUTE_LEDGER } from '../../runtime/src/route-ledger';
+
+describe('route ledger ↔ @objectstack/client surface', () => {
+  const client = new ObjectStackClient({ baseUrl: 'http://localhost:9' });
+
+  const resolve = (path: string): unknown =>
+    path.split('.').reduce<unknown>((o, k) => (o == null ? o : (o as Record<string, unknown>)[k]), client);
+
+  it('every ledger entry naming a client method resolves to a real function', () => {
+    const broken = ROUTE_LEDGER.filter((e) => e.client != null)
+      .filter((e) => typeof resolve(e.client!) !== 'function')
+      .map((e) => `${e.route} → client.${e.client}`);
+    expect(
+      broken,
+      `Ledger entries claiming a client method that does not exist: ${broken.join('; ')}`,
+    ).toEqual([]);
+  });
+});

packages/runtime/src/route-ledger.conformance.test.ts

@@ -21,14 +21,6 @@
  */
 
 import { describe, it, expect } from 'vitest';
-// Relative import of the BUILT client, NOT a package dependency:
-// @objectstack/client's own devDependencies already point back at runtime
-// (its Hono tests boot a real server), so a runtime→client package edge would
-// close a turbo build cycle. Importing the dist keeps the graph acyclic — and
-// CI's Test job always runs after Build, so the dist is present. (The client
-// SOURCE can't be imported here: its module graph resolves through runtime's
-// vitest aliases and breaks on subpath imports like @objectstack/core/logger.)
-import { ObjectStackClient } from '../../client/dist/index.mjs';
 import { HttpDispatcher } from './http-dispatcher.js';
 import { ROUTE_LEDGER, LEGACY_CHAIN_PREFIXES } from './route-ledger.js';
 
@@ -73,22 +65,13 @@ describe('route ledger ↔ dispatcher domain registry', () => {
   });
 });
 
-describe('route ledger ↔ @objectstack/client surface', () => {
-  const client = new ObjectStackClient({ baseUrl: 'http://localhost:9' });
-
-  const resolve = (path: string): unknown =>
-    path.split('.').reduce<unknown>((o, k) => (o == null ? o : (o as Record<string, unknown>)[k]), client);
-
-  it('every `sdk`/`mismatch` entry names a client method that actually exists', () => {
-    const broken = ROUTE_LEDGER.filter((e) => e.client != null)
-      .filter((e) => typeof resolve(e.client!) !== 'function')
-      .map((e) => `${e.route} → client.${e.client}`);
-    expect(
-      broken,
-      `Ledger entries claiming a client method that does not exist: ${broken.join('; ')}`,
-    ).toEqual([]);
-  });
-
+// The client-instance direction — "every named client method actually exists"
+// — lives in packages/client/src/route-ledger-coverage.test.ts, next to the
+// SDK it introspects. It cannot live here: a runtime→client edge (package OR
+// dist import) is unbuildable — client's own devDeps point back at runtime
+// (turbo rejects the cycle), and CI's per-package test tasks build only their
+// own dependency closure, so the client dist does not exist for this suite.
+describe('route ledger hygiene', () => {
   it('every `sdk` entry names its client method; every non-sdk entry carries a rationale', () => {
     const sdkWithout = ROUTE_LEDGER.filter((e) => e.disposition === 'sdk' && !e.client).map((e) => e.route);
     expect(sdkWithout, 'sdk-disposition entries missing a client method name').toEqual([]);