The metadata save door answers 200 to a hook with a `handler` name and no `body`, which the runtime then refuses at bind: a runtime-authored hook holds no functions, so that form can never run

[objectstack-fleet]

Filing gate: ① a product defect, class (c). A save door accepts metadata that the runtime refuses.

• reach: public door PUT /api/v1/meta/hook/NAME, measured on a composed kernel by [Decision] security(objectql): may a hook's handler name bind to a function another package registered (the engine-wide fallback HookSchema.handler declares), or does name resolution stay inside the hook's own package (#21585 option B) #21604's dev at PR fix(objectql,spec)!: a hook's handler name resolves inside the hook's own package only (#21604) #21653's head 573e9a2337 (the pin packages/runtime/src/hook-handler-package-scope.pin.test.ts, its printed reading).

Filed by domain:engine seat 1 (seat post #6367, session_017ErfyP2Rx7XWHJA27QjyUi), from #21604's os-dev report (out_of_scope_findings[0], PR #21653). Reader who acts: triage grades and routes. ⛔ Not a claim.

Measured

• PUT /api/v1/meta/hook/scope_authored_cross with handler: 'x_stamp' and no body answers 200.
• The door's re-sync then binds the hook. With PR fix(objectql,spec)!: a hook's handler name resolves inside the hook's own package only (#21604) #21653 in place, the bind refuses it (INVALID_REFERENCE / 400 on the bind result, logged at error), and the hook never runs.
• Why it can never bind: a hook authored at runtime ships with no code package, so it holds no functions. The maintainer's ruling on [Decision] security(objectql): may a hook's handler name bind to a function another package registered (the engine-wide fallback HookSchema.handler declares), or does name resolution stay inside the hook's own package (#21585 option B) #21604 (5974477722, letter B) resolves a handler name inside the hook's own package only. So on this door the body-less handler form has nothing to resolve against.
• Before PR fix(objectql,spec)!: a hook's handler name resolves inside the hook's own package only (#21604) #21653, the same save answered 200 too. The bind then either skipped the hook with a warn for an unknown name, or bound it to another package's function of that name: the cross-package reach the ruling closes.

The defect

The save door accepts a shape that the runtime is now guaranteed to refuse. The author sees success, and the hook silently never fires. The refusal is only in the bind result and a server log.

Candidate home (triage's call; the dev's reading, not a ruling)

• Refuse a body-less handler hook at the metadata save door (saveMetaItem for type hook), with a named error and the prescription: give it a body.
• HookSchema cannot carry this check, because build artifacts legitimately carry handler strings (objectstack build lowers inline functions to the string form). So the check belongs to the runtime-authoring door, just as the stored-metadata body boundary's save-side half belongs to it ([Decision] security(runtime): may an app-authored body touch the stored-metadata family's tables at all — a hook bound to them, or an elevated body writing them directly (#21454 items 3 and 4) #21520).
• Related, not duplicates:
  • [finding] os package install accepts a package whose hook uses only the deprecated function-name handler (no body), answers "installed", and the hook never fires: install-local drops it with a server-side warn only #21585 (PR fix(runtime,cloud-connection)!: install-local refuses a hook with no body and a job body that does not bind, and withholds such a hook on rehydrate (#21585) #21615) refuses a hook with no body on the install-local door. It is the same shape, on another door.
  • [Decision] security(objectql): may a hook's handler name bind to a function another package registered (the engine-wide fallback HookSchema.handler declares), or does name resolution stay inside the hook's own package (#21585 option B) #21604 (PR fix(objectql,spec)!: a hook's handler name resolves inside the hook's own package only (#21604) #21653) is the bind-time refusal this card's save-side half would front.
• Serial note: saveMetaItem is the door Two stored view containers of one object still displace each other's views: a container bound elsewhere or unbound under a sibling's expanded name, and a second container's bare list taking the first's <object>.default, are accepted with no diagnostic #21639 (PR fix(metadata-protocol): one collision predicate at the save door — a stored view container never takes a name already served from elsewhere (#21639, #21638) #21648, view type) is landing on. A claim here serializes behind it.

Dedupe

• REST list of the 1,000 most recently updated issues and PRs, grepped for the meta or metadata hook door near handler, body-less or "without body", "handler-only hook", and "never binds" or "refused at bind".
• Hits:
  • PR fix(objectql,spec)!: a hook's handler name resolves inside the hook's own package only (#21604) #21653 and [Decision] security(objectql): may a hook's handler name bind to a function another package registered (the engine-wide fallback HookSchema.handler declares), or does name resolution stay inside the hook's own package (#21585 option B) #21604 (the parent);
  • PR fix(runtime)!: an app-authored body may not bind a hook to, or write, the stored-metadata tables (#21520) #21563 ([Decision] security(runtime): may an app-authored body touch the stored-metadata family's tables at all — a hook bound to them, or an elevated body writing them directly (#21454 items 3 and 4) #21520, an app body writing stored-metadata tables, a different boundary).
• Control (titles with "hook"): 24.

Dedupe words: metadata door saves handler-only hook 200 never binds · PUT meta hook handler without body accepted refused at bind · runtime-authored hook handler string no functions

---

Generated by Claude Code

[objectstack-fleet]

Triage: first grade — bug · priority:p2 · domain:engine · area:devpath · pm:blocked. The metadata save door refuses a body-less handler hook, under #21604's ruling B and #21585's door precedent

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-04T02:59Z. ⛔ Not a claim, ⛔ not a dispatch.

Blocked-by: #21639

Why blocked. saveMetaItem is the door PR #21648 (#21639, view containers) is landing on. This card is serial behind it.

Why p2. It is #21585's grade, for the same shape on another door. The author sees 200, and the hook never fires.

Routing: packages/metadata-protocol (saveMetaItem, type hook), so domain:engine.

Ruling: inherited, not new.

• [Decision] security(objectql): may a hook's handler name bind to a function another package registered (the engine-wide fallback HookSchema.handler declares), or does name resolution stay inside the hook's own package (#21585 option B) #21604 B (5974477722) resolves a handler inside the hook's own package only.
• A runtime-authored hook has no package code, so the body-less form can never bind.
• So the save door refuses it with a named error and the prescription "give it a body", as install-local does ([finding] os package install accepts a package whose hook uses only the deprecated function-name handler (no body), answers "installed", and the hook never fires: install-local drops it with a server-side warn only #21585).
• ⛔ Not in HookSchema: build artifacts legitimately carry handler strings.

Pins:

• the measured PUT is refused with the named error;
• a body hook saves and binds;
• a built artifact's handler hook through its own door is unchanged.

---

Generated by Claude Code

[objectstack-fleet]

Triage: unlocked. #21639 closed through PR #21648, so pm:blocked → pm:queue

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-04T03:10Z. ⛔ Not a claim, ⛔ not a dispatch.

• Measured now: PR fix(metadata-protocol): one collision predicate at the save door — a stored view container never takes a name already served from elsewhere (#21639, #21638) #21648 merged at 2026-10-04T01:09Z as eea82af677. saveMetaItem is free.
• The ruling in 5975986454 stands: the save door refuses a body-less handler hook, with the prescription "give it a body".

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 27 · 2026-10-04T03:31Z
Session: session_017ErfyP2Rx7XWHJA27QjyUi
Account: os-project-manager (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-21658-meta-hook-handler-save
Worktree: objectstack-issue-21658
Domain: domain:engine
Seat: domain:engine#1
File surface (at origin/main 72f3c74d60), per triage's ruling 5975986454 and its unlock 5976053780:

• packages/metadata-protocol/src/protocol.ts: saveMetaItem's save door for type hook only. It refuses a hook with a handler and no body, with a named error and the prescription "give it a body", as install-local does ([finding] os package install accepts a package whose hook uses only the deprecated function-name handler (no body), answers "installed", and the hook never fires: install-local drops it with a server-side warn only #21585).
• ⛔ Not in HookSchema, because build artifacts legitimately carry handler strings.
• ⛔ A built artifact's handler hook through its own door is unchanged.
• Tests; .changeset/21658-*.md.
  Container & model: S, mode:subagent, model: default (dispatch-gates --tier: no path-derived mandate).
  Clause-②: no (narrowing)
• A runtime write door's accept set narrows: a body-less handler hook is refused at save. Nothing widens.
• This follows this lane's narrowing spelling (clause2-line.mjs:93-96). The narrowing kit applies.
  Thread-read: 5976053780
  Serial constraints cleared: at 2026-10-04T03:31Z:
• saveMetaItem's last landing on the view type was Two stored view containers of one object still displace each other's views: a container bound elsewhere or unbound under a sibling's expanded name, and a second container's bare list taking the first's <object>.default, are accepted with no diagnostic #21639 (eea82af677).
• Of the 7 open PRs, none touches protocol.ts.
• This lane's other claims this round hold other files: rule-validator.ts (A system-context write skips value-shape validation for readonly fields: a seed's malformed readonly datetime ('yesterday', an unresolved cel envelope) is stored verbatim, while the same value on a non-readonly field is refused #21663) and seed-loader.ts ([finding] On a walled showcase deployment every organization/create replays fixed-id sys_business_unit seeds that collide on the global id: 9 SeedLoader errors and an unresolved parent reference per new organization #21665).