Retire the plural `/meta/objects/:name/state/:field` registration: SDK moves to the singular twin, the collision's registration-order pin is deleted (step ② of the #9180 ruling)

[os-zhuang]

Step ② of the #9180 ruling (/meta type segment is ALWAYS singular), carved by the spec seat under the maintainer's direct reassignment (2026-08-19, verbatim: 「改派给 spec 席,现在就拆」; audit comment #9180 comment 5349687344).

The ruling being implemented (⛔ not re-litigable)

Maintainer re-weigh, 2026-08-17 (#9180 comment 5311434183), verbatim, untranslated:

「② 照原样做；只需要修正 objectstack objectui cloud 中错误的写法。」

Operative text from the ruling record: point meta.getLegalNextStates at the singular twin, delete the plural registration, delete the registration-order pin the collision required.

Measured anchors (2026-08-19, origin/main — re-verify at your branch point)

• packages/rest/src/rest-route-ledger.ts:195 — GET /api/v1/meta/objects/:name/state/:field, disposition: 'sdk', client: 'meta.getLegalNextStates' (the plural row)
• packages/rest/src/rest-route-ledger.ts:197 — GET /api/v1/meta/object/:name/state/:field, disposition: 'server-only' (the singular twin — already mounted)
• packages/rest/src/rest-server.ts:6016-6040 — the mount (${metaPath}/${objectsSegment}/:name/state/:field)
• packages/client/src/index.ts:873 — the SDK method whose route string moves (one string in our own SDK)
• packages/rest/src/meta-route-registration-order.test.ts — the order pin that exists only to manage the collision; deleted with it
• packages/runtime/src/route-ledger.ts:352 — the dispatcher-ledger mirror row for the plural spelling; measure whether it moves in the same stroke (ledgers must stay honest to what is mounted)

Constraints that ride verbatim

• model: claude-fable-5 floor, no downward discretion — standing note on the ruling anchor ([Ruling] The /meta type segment is ALWAYS singular — retire every plural spelling, no exception, in three steps #9180 comment 5310450985): every step of this ruling is a contract accept/reject or published-surface change; ⛔ do not dispatch or execute below the floor.
• ⛔ NOT in scope (re-weigh item 3): the boundary fold (META_URL_TO_SINGULAR) stays as a compatibility tolerance for external callers; no new refusals beyond what step ① (PR fix(metadata): route the three read-side /meta verbs through the canonical type boundary (#9157) #9191) already shipped. This card moves a registration and an SDK string; it does not widen the refusal set. If your measurement shows the plural registration's deletion would newly refuse a spelling the fold currently accepts, STOP and report the fork — do not pick a side.
• Docs whose prose names the plural state route (release pages are read-only) follow the docs card, not this one.

Dedup checked 2026-08-19: no existing step-② card (search: getLegalNextStates plural/singular registration — zero open or closed matches beyond the anchor).

Part of #9180.

---

Hold state

⚠️ Appended 2026-08-20 by the domain:cli seat (session session_019bmVFqoQPq63zhKrxdYG1r) — everything above is the filing seat's text, unmodified. This section is the machine-readable exit for the pm:on-hold I applied, and belongs in the body: the H9 predicate reads issue.body only, so the Restart-when: I first wrote in comment 5349822290 could never fire. Rationale and full context stay in that comment.

Restart-when: claude-fable-5 capacity is available again — re-tested by the domain:cli seat every patrol (~60 min)

⛔ Do not dispatch this below the claude-fable-5 floor while held. The 2026-08-13 general quota accommodation (「fable 如果用完了，可以用 opus」) does not reach a floor set by a later card-specific ruling; if fable is unavailable, the card waits.

[os-elon]

Claim: PM loop round 29
Session: session_019bmVFqoQPq63zhKrxdYG1r
Branch: claude/issue-10077-meta-state-route-singular
Worktree: objectstack-issue-10077
Domain: domain:cli
File surface: packages/rest/src/rest-route-ledger.ts · packages/rest/src/rest-server.ts · packages/rest/src/meta-route-registration-order.test.ts · packages/client/src/index.ts · packages/runtime/src/route-ledger.ts · .changeset/** (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: claude-fable-5
Clause-②: yes
Serial constraints cleared: 🔓 free — measured, see below.

⛔ The tier is MANDATED, not chosen — and it is not downgradeable

The ruling anchor (#9180 comment 5310450985) carries a standing claude-fable-5 floor with no downward discretion, and this card repeats it verbatim: "⛔ do not dispatch or execute below the floor."

⚠️ The 2026-08-13 quota exemption (「fable 如果用完了，可以用 opus」) does NOT apply here. That exemption's object is dispatch under measured fable unavailability; it is a general accommodation and ⛔ cannot license execution below a floor an explicit ruling set. This seat's ruling ② additionally records the one-time downgrade as SPENT. ⇒ If fable is unavailable, the correct action is ⛔ do not dispatch, report the unavailability — not substitute a tier.

Because the dispatch tier is CONTRACT_REVIEW_TIER, the Clause-② enqueue gate is satisfied by construction and ⛔ no needs:contract-review is incurred. I declare Clause-②: yes on the conservative reading: the ruling anchor already classified every step of #9180 as a contract / published-surface change, and this one deletes a registered route.

Serial constraints — measured, and ⚠️ the first measurement was an artifact

Open PRs are the in-flight set (12 open). The only candidates touching my packages are #10060 (packages/rest/src/package-routes.ts, packages/runtime/src/domains/packages.ts) and #10058 (packages/lint/**). Neither touches any file in my surface. Ruling ① exempts same-package/different-file, so nothing is owed even for #10060. ⇒ Zero collisions on all five files.

⚠️ ⭐ Worth carrying: my first pass produced a false contention signal. Diffing every claude/* remote head with recent commits against the surface returned 11 branches all reporting the identical three files (client/src/index.ts, plugin-dev/src/dev-plugin.ts, rest/src/rest-server.ts). That is a stale-merge-base artifact — those branches carry merges from main, so diff merge-base..head re-reports main's own progress as if it were the branch's changes. None of the 11 has an open PR. ⇒ ⛔ Do not clear (or declare) serial constraints from a bare claude/* head sweep; the honest population is open PRs, and the honest comparison is the PR's own file list.

Scope fence

⛔ This card does not widen the refusal set. The boundary fold (META_URL_TO_SINGULAR) stays; re-weigh item 3 defers the external break. If your measurement shows deleting the plural registration would newly refuse a spelling the fold currently accepts, STOP and report the fork — ⛔ do not pick a side. That is a reportable finding, not a judgement call delegated to you.

⚠️ packages/client/src/index.ts is hard-serialised with #10078 (step ③, also in this lane). #10078 is held until this lands. ⛔ Do not touch the item-route typing family (getItem / saveItem / deleteItem / getHistory) — only the getLegalNextStates route string at :873 is yours.

---

Generated by Claude Code

[os-elon]

⛔ CLAIM WITHDRAWN — measured Fable exhaustion. pm:dispatched → pm:on-hold, assignee cleared.

Restart-when: claude-fable-5 capacity is available again — re-tested by the domain:cli seat on every patrol (~60 min). ⛔ This condition names a live owner on purpose; it is not delegated to "the next card that comes along."

domain:cli seat, session session_019bmVFqoQPq63zhKrxdYG1r, round 29. The claim comment 5349803796 stays up unedited — it is the record of what I committed to before I knew the outcome.

What happened

Dispatched at the mandated claude-fable-5 floor at 00:5xZ. The agent terminated early on an API error, verbatim:

You've reached your Fable 5 limit. Switch to another model, or manage usage credits at claude.ai/settings/usage to continue.

Nothing was implemented. No branch was created, no worktree, no commits, no PR. The card is exactly as it was before I claimed it.

⛔ Why I did NOT re-dispatch this at opus

I wrote the answer into the claim comment before the failure, which is the only reason I trust it now:

"If fable is unavailable, the correct action is ⛔ do not dispatch, report the unavailability — not substitute a tier."

The reasoning, restated so it can be checked rather than taken on trust:

• The maintainer's 2026-08-13 quota accommodation is verbatim 「fable 如果用完了，可以用 opus」 — a general standing accommodation, and this is genuine measured unavailability, so on its face it applies.
• But [Ruling] The /meta type segment is ALWAYS singular — retire every plural spelling, no exception, in three steps #9180's tier floor (comment 5310450985, carried into the 2026-08-17 re-weigh) is later and specific to this ruling, and it forecloses exactly this substitution in as many words: "⛔ do not dispatch or execute below the floor."
• A later, card-specific ⛔ governs an earlier general accommodation. And this seat's ruling ② already records the one-time downgrade as SPENT.

⇒ Downgrading would be the seat quietly overruling a maintainer's explicit floor on a contract / published-surface change — the precise class the floor exists to protect. ⛔ Not mine to do.

⚠️ The tension is real, and it is the maintainer's to resolve if they want to

Stated factually, ⛔ not as a request and ⛔ not as a nag: the 2026-08-13 accommodation and the 2026-08-17 floor now point in opposite directions on this card. I have resolved it conservatively (floor wins, work waits). If the maintainer intends the accommodation to reach ruling-level floors too, saying so once unblocks this card and every other #9180 step.

⛔ I am not asking for that and ⛔ not blocking on an answer — the quota reset resolves this on its own, and my patrol will catch it.

State

• Retire the plural /meta/objects/:name/state/:field registration: SDK moves to the singular twin, the collision's registration-order pin is deleted (step ② of the #9180 ruling) #10077 — pm:on-hold, unassigned, restart condition above. ⛔ Not abandoned; re-tested every patrol.
• Internal /meta spelling corrections in objectstack: SDK item-route typing normalizes toward singular; metadata-api.mdx stops teaching the plural as a co-equal form (step ③ residue of #9180) #10078 (step ③) — stays pm:blocked behind this card. ⚠️ Its serial was on packages/client/src/index.ts and nothing has moved there, so the hold still stands on its original terms.
• Sibling dispatched the same round, unaffected and in flight: plugin-dev's "no security services" warning cannot fire for a SecurityPlugin whose start() bailed — the three slots it probes are registered in init(), before the bail #10036 at opus.

---

Generated by Claude Code