finding: `objectstack build` lowers a hook body calling `ctx.api.object('x').create()` although the QuickJS sandbox installs no `create` leaf — the extractor ledger advertises the verb, the lint rules read it as a live write, and the body throws `TypeError: not a function` on its first run

[claude]

Found while landing #15394 (PR #16248), out of that card's scope; filed unassigned.

What was measured (origin/main 159dbad)

• The host ObjectRepository (packages/objectql/src/engine.ts, class ObjectRepository) declares create(data) as an alias of insert(), and the spec contract (packages/spec/src/contracts/scoped-context.ts:154) declares insert only.
• The QuickJS installCtx (packages/runtime/src/sandbox/quickjs-runner.ts:556) installs exactly insert / update / delete / updateMany / deleteMany / upsert as ctx.api.object() write leaves — no create. An L2 body calling ctx.api.object('x').create({ ... }) therefore throws TypeError: not a function at run time, and under a hook's default onError: 'abort' that aborts the triggering write with a message naming no member (the same blind message A hook cannot elevate, so a hook-written computed column cannot be protected by field-level editable: false — the guard and the writer are the same door #14010 measured for sudo()).
• Nothing refuses the shape at build time. FORBIDDEN_PATTERNS in packages/cli/src/utils/extract-hook-body.ts:170 refuses .sudo( for exactly this reason (A hook cannot elevate, so a hook-written computed column cannot be protected by field-level editable: false — the guard and the writer are the same door #14010) but has no .create( entry; the shared extractor ledger HOOK_BODY_WRITE_PATTERNS (packages/lint/src/validate-hook-body-writes.ts:230) advertises the syntax as .insert({...}) | .create({...}) | .update({...}) | .updateById(id, {...}) and API_WRITE_METHODS maps create to payload argument 0, so hook-body-write-unknown-field grades a .create() payload as a live write and stays silent when the field exists.
• finding: the flow and hook readonly rules still carry the superseded "INSERT is engine-exempt" premise as a scan gap — a non-system create_record / ctx.api.insert of a readonly column is now a silent no-op nothing reports at build time #15394 deliberately kept .create() OUT of hook-api-update-readonly-field's subject set for this reason (pinned as READONLY_HOOK_METHOD_EXCLUSIONS in validate-readonly-hook-writes.ts): a "silently dropped" finding about a call that throws would be false. That exclusion is correct but leaves the author with no build-time signal at all.

Suggested shape

Refuse .create( at lowering the way .sudo( is refused (a FORBIDDEN_PATTERNS entry whose reason names .insert() as the spelling the sandbox has), and drop create from the extractor's advertised api-crud-literal syntax and API_WRITE_METHODS so the advisory rule stops grading a call that cannot run. Alternatively install a create alias in installCtx — but the spec contract declares insert only, so the refusal is the contract-first route.

Not this

The host-side ObjectRepository.create() alias is reachable by in-process handlers and actions and is not the defect; only the L2 body surface is.

---

Generated by Claude Code