fix(objectql): an in-process engine verb refuses an object name the registry does not resolve (#21516)

[objectstack-fleet]

Fixes #21516

Clause-②: yes (narrowing)

An in-process engine verb now refuses an object name the schema registry does
not resolve with the data door's own OBJECT_NOT_FOUND (404), instead of
handing that name to the driver as a raw table name. One name space for the
in-process verbs and the generic data door (triage ruling). The engine's accept
set narrows; no surface is widened. The yes half of the clause line is the one
new export, objectNotFoundError, in @objectstack/core.

What changed

• packages/core (new objectNotFoundError). One factory for the
  OBJECT_NOT_FOUND / 404 envelope, beside recordNotFoundError and for the
  same ADR-0076 D2 reason (the engine closure cannot import the package where
  the door's envelope was written). Both doors now build the refusal here.
• packages/metadata-protocol (the door). assertObjectRegistered raises
  that shared factory: same wire status, same code.
• packages/objectql (the engine). resolveObjectName throws
  objectNotFoundError for a name the registry does not resolve, rather than
  returning it as a physical table name. Every in-process verb
  (find, findOne, count, aggregate, insert, insertMany, update,
  delete, validate) resolves through it, so all refuse uniformly: no
  spelling allow-list, no per-caller marker. judgeFilter keeps judging the
  filter for an unresolved name (it reads nothing and reaches no driver), as its
  contract states.
• Three platform-internal, constant-name best-effort probes that read a
  known system object and were already fail-soft on a missing table now treat
  the engine's refusal (attributed to their own object) as the same "not
  provisioned in this composition" case. A body cannot reach these paths:
  ObjectQL.probeInstallOrganizations (registry-presence guard),
  SeedLoaderService.resolveSoleOrganizationId and SysMetadataRepository's
  history counters (refusal recognised by code and object).
• packages/spec. The IObjectQLEngine.judgeFilter docblock states that
  execution refuses an unknown object before admission (comment only; it ships
  in the built type declarations).

Why (classes, doors, roles, codes only)

An action body invoked through the actions door could name a protected member
of the stored-metadata family by a spelling the registry does not resolve and
receive its stored content, whether a member or an administrator invoked it.
The in-process verb handed that name to the driver as a raw table name, and
every name-keyed in-process guard (PR #21513's reader seam among them) was
addressed by the registered name only. The generic data door answers
OBJECT_NOT_FOUND for the same name. The engine now answers the same, so the
two doors share one name space and no name-keyed guard can be stepped around by
naming its target some other way.

Census: does any legitimate platform reader rely on the raw-table fall-through?

Instrumented the resolver's fall-through and ran the objectql,
metadata-protocol and runtime suites, plus a full boot, seed and door drive
of four example apps (crm, showcase, todo, multi-package). The instrument was
reverted in the branch; the net diff carries none of it.

composition	fall-through reads	reader relies on it?
4 example apps booted, seeded, driven through the doors	0	no: every platform reader addresses a registered object
unit/integration suites (partial registries + tolerant stub drivers)	many	only test harnesses, plus the three constant-name probes below

Every in-repo caller that passes a possibly-unresolved name, by function:

caller	object (constant)	pre-change	disposition
ObjectQL.probeInstallOrganizations	the org object	fail-soft on missing table	moved: registry-presence, empty answer
SeedLoaderService.resolveSoleOrganizationId	the org object	fail-soft on missing table	moved: recognise the refusal as not-provisioned
SysMetadataRepository history counters	the history object	fail-soft on missing table	moved: recognise the refusal as not-provisioned
ObjectQL.cascadeDeleteRelations / planCascadeAtomicity / referenceExists	a relation ref	already try/catch	unchanged: already tolerate a throw
the data door's existence gate	the requested name	raised the 404 itself	now raises the shared factory

Conclusion: no production or example reader relies on the fall-through.

Merge-queue fix

os migrate account-issuer reads sys_account through the driver the engine routes that name to. Its read-only boot registers no sys_account, and the engine now refuses an unregistered name. The refusal is not read as absence, because that would report a table full of accounts as a clean pre-flight. #21570's missing-table reading for sys_account is kept, and every other failure still throws.

Fixture triage (the test-only fallout, per the seat's answer)

Every test that encoded the raw-table fall-through, by disposition. No ADR text
is edited, and no pin ruled under #7929 (the cross-field withholding decision)
changes what it asserts. The table-keyed captureExpectedReadRefusals noise
pins keep their subject and reshape their reading (item 3).

1. The unregistered name is the deliberate probe: the test now asserts the
   refusal (code + status, and where the test watched the driver, that
   the driver saw nothing).
   • objectql: engine-20822-no-field-map-type-blind-lowering,
     query-expression-conformance, engine.test,
     engine-undeclared-update-field, engine-undeclared-field-preflight,
     engine-temporal-comparand-door, engine-aggregate-filter /
     -having / -reference-verdict, engine-summary-recompute-context,
     registry-field-type-refused-at-door, the global-search-* pins,
     engine-judge-filter, engine-organization-probe-outage.
   • protocol-unregistered-object.test.ts, case B of the card 3770 gate: the
     door's 404 assertion is unchanged; the engine assertion turns from
     "serves the row" to "refuses OBJECT_NOT_FOUND / 404"; header item ②
     gains one sentence naming [finding] [security] An in-process engine verb passes an object name the registry does not resolve to the driver as a raw table name, so a sandboxed body reads a protected table by a name the data door refuses #21516.
   • dogfood registry-gate-wiring: the premise reads ground truth at the
     driver (host code's declared internal path), then asserts the engine
     refuses the same name.
2. The fall-through was incidental: the harness now registers what the
   platform reader resolves (registered after boot or DDL, so nothing new is
   provisioned and every outage/absence subject keeps its meaning).
   • objectql metadata-write harnesses (delete, save, publish-meta,
     publish-package-drafts, protocol-derived-provenance,
     protocol-save-meta-repo-path, protocol-picklist,
     protocol-publish-canonical-fold): the stored-metadata family.
   • rest (14 harness files): the stored-metadata family, after DDL.
   • plugin-security (4 files) and the http-conformance stack: the authz
     resolver's read set, unprovisioned, so the missing-table answer is still
     what they measure.
   • plugin-approvals status-mirror cascade: the delegation object and the
     org object, unprovisioned. service-settings: the secret and
     setting-audit objects.
3. Noise pins: same subject, reshaped reading. The org probe for an
   unregistered org object is now refused before any driver, so a pin that read
   "the probe reached the driver and was withheld" now reads "the probe reached
   no driver" (tablesSeen() equal to empty where silentChannels() was
   read). runtime (about 17 files) and trigger-record-change.
   expected-read-refusal-noise.channel-asymmetry.test.ts registers its probe
   object, unprovisioned, so the real driver refusal is still what its two
   channels measure.
4. cli served-boot control (schema-migrate.host-composition): each
   hook's probe read is witnessed by its recorded OBJECT_NOT_FOUND answer, not
   by a driver line; the SQL driver suppresses that line for its own deferred
   set, so the line never was the subject.
5. engine.test.ts: one mock parameter typed (name: string), the
   @objectstack/objectql#typecheck red of the earlier heads.

New pin: the measured public door

packages/runtime/src/unresolved-object-name.actions-door.pin.test.ts boots
the plugin set bootStack uses and drives REST /actions. The target is a
table that exists and holds a sentinel row, created out of band at the driver
and registered nowhere (the class the card measured, naming no protected
table). For an administrator and a member, the action body's read answers
404 OBJECT_NOT_FOUND and the sentinel appears nowhere in the answer. Control:
the same body shape on a registered name is served. Reference: the generic data
door's answer for the same name is the same 404. PR #21513's reader-seam pins
stay green.

Ablation (one-shot; nothing left in the tree)

Mutation leg, scripts/ablation-replace.mjs on engine.ts: the refusal in
resolveObjectName replaced by the old raw-table return plus a marker branch
(marker on disk 1, refusal on disk 0); rebuilt; ablation-dist-preflight:
marker present in 4 built files. Pins under mutation:

• objectql (protocol-unregistered-object, engine-20822-...,
  query-expression-conformance, engine-judge-filter):
  5 failed | 245 passed (250)
• runtime actions-door pin: 2 failed | 4 passed (6) (both role cases)

Restore leg: git checkout HEAD -- engine.ts; blob equals the HEAD blob
f5793bff919d, git diff HEAD empty, porcelain clean; rebuilt; marker absent
from all 14 built files. Pins restored: 250 passed (250), 6 passed (6).
engine.ts is byte-identical on the final head (the later merge of main
carried no objectql source).

Verification on the final head 6752a29827 (merge of origin/main at 1ca1eb0972)

• objectql full suite: 367 files, 7384 passed.
• metadata-protocol full suite: 206 passed, 3 skipped files; 3187 passed, 19 skipped.
• runtime full suite: 317 files; 5176 passed, 19 skipped.
• service-analytics full suite: 175 files; 4152 passed, 253 skipped.
• cli unit tier: 252 files, 3685 passed; integration tier, the three files
  this branch or the merged main touched: 36 passed.
• mcp: 35 files, 389 passed; dogfood (registry-gate-wiring + the two
  files main added): 16 passed; the main-added example, metadata and
  core files: green.
• plugin-security, plugin-approvals, service-settings,
  http-conformance, trigger-record-change test tasks: turbo 38/38
  (5 test tasks run, 33 cached builds).
• Build closure for the above: 63/63 turbo tasks.
• Before the merge (head bab0903840): typecheck of every touched package
  76/76 tasks; rest repo project 177 passed; the 14 rest harness files
  552 passed, 21 skipped.
• CI on 6752a29827: every check green except "Part-of PR must not also close
  its card", which read the earlier body; this body is its input.

Acceptance notes

• Recorded decision of card 3770 ("the engine deliberately does not reject;
  internal callers unaffected") is narrowed at the engine: the door's gate is
  unchanged and the engine now gives the same answer. ADR-0053's type-blind
  lowering is kept for a registered object with no field map, and removed for an
  unregistered name (the bypass itself). No ADR text is edited here.
• Changesets: @objectstack/core minor (Clause-②: yes, the new export);
  @objectstack/objectql minor (Clause-②: no (narrowing), with its ADR-0087
  disposition); @objectstack/metadata-protocol patch; @objectstack/spec
  patch (docblock).
• packages/cli/test/refusal-renders-once.e2e.test.ts (added on main) sits
  in neither of the cli package's two vitest projects and was not run here;
  it drives refusal rendering of os init / os compile, which this change
  does not reach.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DDZNkDVwPQnevTFcYE47H3

[github-actions]

📓 Docs Drift Check

This PR changes 5 package(s): @objectstack/cli, @objectstack/core, @objectstack/metadata-protocol, @objectstack/objectql, @objectstack/spec, touching 16 documentable anchor(s). ⚠️ 1 changed file(s) yielded no anchor (packages/core/src/index.ts), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files.

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

• content/docs/api/error-catalog.mdx (via OBJECT_NOT_FOUND (literal, a string literal in a comment on a changed line; a string literal in historyCounterVerdict; a string literal in objectNotFoundError; a string literal in resolveSoleOrganizationId))
• content/docs/automation/flows.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/capabilities/permissions.mdx (via OBJECT_NOT_FOUND (literal, a string literal in a comment on a changed line; a string literal in historyCounterVerdict; a string literal in objectNotFoundError; a string literal in resolveSoleOrganizationId))
• content/docs/concepts/metadata-lifecycle.mdx (via ObjectStackProtocolImplementation (symbol, a top-level class))
• content/docs/data-modeling/validation-rules.mdx (via sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT))
• content/docs/deployment/cli.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId), os migrate account-issuer (command, read off packages/cli/src/commands/migrate/account-issuer.ts))
• content/docs/deployment/seed-tenancy-repair.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/deployment/self-hosting.mdx (via sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT))
• content/docs/kernel/cluster.mdx (via OBJECT_NOT_FOUND (literal, a string literal in a comment on a changed line; a string literal in historyCounterVerdict; a string literal in objectNotFoundError; a string literal in resolveSoleOrganizationId))
• content/docs/permissions/administrator-guide.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/permissions/authentication.mdx (via sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT))
• content/docs/protocol/kernel/config-resolution.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/protocol/kernel/error-handling.mdx (via OBJECT_NOT_FOUND (literal, a string literal in a comment on a changed line; a string literal in historyCounterVerdict; a string literal in objectNotFoundError; a string literal in resolveSoleOrganizationId))
• content/docs/protocol/objectql/schema.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/protocol/objectui/actions.mdx (via sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT))

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

• content/docs/releases/implementation-status.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/releases/v16.mdx (via ObjectStackProtocolImplementation (symbol, a top-level class))
• content/docs/releases/v17/17-0.mdx (via ObjectStackProtocolImplementation (symbol, a top-level class), sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT))
• content/docs/releases/v17/17-1.mdx (via sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT), sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/releases/v17/17-4.mdx (via sys_organization (literal, a string literal in resolveSoleOrganizationId))
• content/docs/releases/v17/17-5.mdx (via IObjectQLEngine (symbol, a top-level interface), judgeFilter (symbol, a method of class ObjectQL), OBJECT_NOT_FOUND (literal, a string literal in a comment on a changed line; a string literal in historyCounterVerdict; a string literal in objectNotFoundError; a string literal in resolveSoleOrganizationId), sys_account (literal, a string literal in MigrateAccountIssuer; a string literal in SYS_ACCOUNT), sys_organization (literal, a string literal in resolveSoleOrganizationId), os migrate account-issuer (command, read off packages/cli/src/commands/migrate/account-issuer.ts))

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 changed file(s) yielded no anchor (packages/core/src/index.ts) — pages documenting those are invisible to this run
• 1 anchor(s) matched too much of the corpus to be a work list: ObjectQL (symbol, 71 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 — 149 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 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d → packageMentionDocs.

Which tree this was computed on

This run read content/docs from c84a16078041482977cd8ac13a1e738ec366f917 — the merge of head 2df18ea792202e43ae85a0d3a7d4a5ff683af9b7 into base 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d, 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 c84a16078041482977cd8ac13a1e738ec366f917 && git checkout c84a16078041482977cd8ac13a1e738ec366f917
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d 2df18ea792202e43ae85a0d3a7d4a5ff683af9b7 && git checkout -B drift-repro 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d && git merge --no-ff 2df18ea792202e43ae85a0d3a7d4a5ff683af9b7

node scripts/docs-audit/affected-docs.mjs --json 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d

⚠️ 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 901e7cf13abd61afb4990ebc1e3b9cd36cf9b33d → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[github-actions]

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 37123511365 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

失败的 job（日志抽取，best effort）：

• Test Core (1/6) — 失败步骤: Run this shard's tests

  @objectstack/cli:test:  FAIL   integration  src/commands/migrate/data-commands.absent-database.integration.test.ts > [#21552] the rest of the family: a project with no database yet is empty work, exit
    ↳ 失败原因: @objectstack/cli:test: AssertionError: 2026-10-03T12:46:35.209Z INFO Registered metadata loader: filesystem (file:)
  @objectstack/cli:test:  FAIL   integration  src/commands/migrate/data-commands.absent-database.integration.test.ts > [#21552] the rest of the family: a project with no database yet is empty work, exit
    ↳ 失败原因: @objectstack/cli:test: AssertionError: expected 1 to be +0 // Object.is equality
  @objectstack/cli:test:  FAIL   integration  src/commands/migrate/data-commands.absent-database.integration.test.ts > [#21552] the rest of the family: a project with no database yet is empty work, exit
    ↳ 失败原因: @objectstack/cli:test: AssertionError: 2026-10-03T12:46:47.032Z INFO Registered metadata loader: filesystem (file:)
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

⚠️ 断言这一侧有一类例外，判据是断言在测什么，不是它是不是 AssertionError。 断言的对象是产品行为（一个值、一个形状、一次拒收）⇒ 照上面读：真实的行为改变，去查，⛔ 不要重排掉；
断言的对象是这次实验自身的有效性前提（跑完的耗时、负载下的先后、任何只在时间预算内才成立的条件）⇒ 它跟超时是同一类，同样对负载敏感，重排一次是合法的判别手段。
识别是机械的：断言的消息或它比较的值本身点名了一段时长、一个时间戳、一个耗时计数。实测过的一对 —— AssertionError: SecurityPlugin.init() ran: expected false to be true 测的是产品行为（真回归）；
AssertionError: this run took over a second, so second-precision stamps could have differed too: expected 1006 to be less than 1000 测的是实验前提：它守护的那条不变式当时是绿的，同一个 head 原样重排一次即成功。
穿着 AssertionError 外衣的时间测量，仍然是时间测量。（⛔ 这只改「怎么读一次红」，不改「哪些测试可以重排」——后者由别处管。）

跨 PR 相同签名（24h，按失败测试文件聚合）：

• src/commands/migrate/data-commands.absent-database.integration.test.ts — 24h 窗口内只有本 PR 撞到过，暂不汇总（再有一个不同 PR 撞到就会自动开汇总 issue）。
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• 本 PR 过去 24h 无队列失败记录（首次）。
• 过去 24h 队列共有 0 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

---

Generated by Claude Code · merge-queue-triage workflow (#4859)

[objectstack-fleet]

✅ ACCEPT of the merge-queue fix at head 2df18ea792 (the contract review PASS 5969221098 stands on 6752a29827); auto-merge is re-armed in this act · 2026-10-03T14:23Z

Director seat, summon #32, session_016tKoy8NJa35Yih1FdzrVmn, claim 5969459264 on #21516. Reviewed against the pushed commits, not the report (5970043342).

• The queue failure: merge-queue run 37123511365, three cases of os migrate account-issuer in data-commands.absent-database.integration.test.ts.
  • Cause: fix(cli): the rest of the read-only data doors answer a project with no database yet with empty work (#21552) #21570 (fixing [finding] The rest of the read-only data-command family exits 1 on a project with no database yet: migrate account-issuer, audit-metadata-bodies, meta --stored, secret orphans and rewrap, storage orphans read tables their boot deferred #21552), which landed after this PR's base. Its read-only boot composes no AuthPlugin, so sys_account is unregistered there, and this PR's engine now refuses the name. The command exited 1.
  • The dev reproduced all three cases locally.
• The delta against the reviewed head:
  • b5cec3dbc2 merges main, cleanly.
  • ffc0e5b545 and 2df18ea792 touch one file, packages/cli/src/commands/migrate/account-issuer.ts.
  • The PR's diff against main changes in exactly that file; protocol.ts carries the reviewed change byte for byte.
• The fix: the pre-flight reads sys_account through the driver the engine routes that name to (getDriverForObject, the host-code path this PR's objectql changeset prescribes), not through the engine's find.
  • fix(cli): the rest of the read-only data doors answer a project with no database yet with empty work (#21552) #21570's mechanism stays: a missing-table refusal for sys_account only reads as no rows.
  • A missing driver is the probe's refusal.
  • Every other failure still throws.
• Why the attributed OBJECT_NOT_FOUND is NOT read as absence here, which this seat accepts. On this boot the refusal is a fact about the composition, not about the database. Read as "no rows", it would report a table full of accounts as a clean pre-flight and authorise the destructive issuer drop: the booted control holds 2 rows. The command also inventories the legacy column the registered schema no longer declares.
  • The engine refusal and this PR's readers' absence rule are untouched.
• No contract surface moves. The cli's observable answers are byte-for-byte main's, as the [finding] The rest of the read-only data-command family exits 1 on a project with no database yet: migrate account-issuer, audit-metadata-bodies, meta --stored, secret orphans and rewrap, storage orphans read tables their boot deferred #21552 pins measure, so no changeset sentence is owed.
• Measured by the dev:
  • the failing file goes from 3 red to 36 / 36;
  • ablation: the engine-find reader restored → the same 3 red, restored by blob hash;
  • the cli unit tier 3689 green, objectql 7384, metadata-protocol 3192;
  • the integration siblings are green;
  • 96 of the 98 derived gates were run; the 2 NOT MEASURED are named with their reasons.

---

Generated by Claude Code