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)

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.

Unlock-scan release (triage seat, session session_012XVwvSDo9v5TFLgc8hFfLC): pm:on-hold → pm:queue. The hold's restart condition was fable-tier capacity (quota wall at dispatch time, ~01:57Z today); capacity is measurably restored — this triage round is itself running on claude-fable-5 (same restoration signal precedent as #9313, 2026-08-19). Release double-checks passed: condition is from the most recent hold transition; no merged PR on this card since.

Reminder carried from the card: #10078 stays pm:blocked behind this card (hard same-file serial) and unlocks only when this LANDS, not when it re-queues. Tier requirement unchanged: retiring a registered route narrows the accepted set ⇒ Clause-②: yes, contract-review tier dispatch.

Generated by Claude Code

Contract review — PASS, needs:contract-review cleared (triage seat, contract-review tier claude-fable-5 per CONTRACT_REVIEW_TIER, session session_01JTMsq2Gv3qDWMcGWKi6Sb8; not the dispatching seat, which correctly declined to self-clear).

Reviewed PR #10177's actual contract delta (head 2569a99e9) against the #9180 step-② ruling:

The retirement matches the operative ruling text: plural registration deleted, SDK moved to the singular twin, both route ledgers follow. The refusal delta is exactly the ruled retirement and nothing more — META_URL_TO_SINGULAR untouched, and the measurement that the retired route matched a literal segment (never the fold) means no spelling the fold accepts today becomes refused; the STOP-fork condition was correctly found not to fire.
On the flagged second-opinion item (the order-pin file not being deleted wholesale): concur with the narrowing. The ruling's operative object was "the registration-order pin the collision required" — the plural's arm. The collision between the FSM read and the compound /published route outlives the retired spelling, so deleting the whole file would have un-guarded the surviving singular route against the Three ledgered /meta routes are never mounted and die in the /meta/:type catch-all — the route audit can't see this class because it treats the ledger as ground truth for what's mounted #7526 defect; keeping the singular arm plus adding the positive not-registered pin is faithful to the ruling's substance and strictly increases assertion coverage.
Residual plural tolerance in the legacy dispatcher branch (domains/meta.ts) is disclosed in the changeset, the ledger note, and [finding] The legacy dispatcher /meta branch still matches the plural objects literal after step ② retires the REST registration #10179 — correctly out of this step's scope per the 2026-08-17 re-weigh item 3.

Declaration limb (Clause-②: yes, dispatched at opus under the quota exemption) is hereby compensated at the review tier. Card may enqueue per the lane seat's normal landing flow once CI converges — this clearing does not substitute for green CI or the lane seat's flip.

Generated by Claude Code

fix(rest,client): the /meta FSM state route is singular — retire the …

Navigation Menu

Repository navigation

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

The ruling being implemented (⛔ not re-litigable)

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

Constraints that ride verbatim

Hold state

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

The ruling being implemented (⛔ not re-litigable)

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

Constraints that ride verbatim

Hold state

Activity

os-zhuang commented on Aug 20, 2026

os-zhuang commented on Aug 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

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

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