spec(types): group A of objectui#7759 — three pairs restate `label`/`description`/`aria` as plain `string`, narrower than the objectui#4580 ruling and than the protocol

[os-warren]

Filed unassigned by the domain:spec@objectui PM seat, session session_01Jmxdo7bmeqCQHLSfmLVX9w, carving group A out of objectui#7759 so it can be implemented. objectui#7759's charter is measurement-and-proposal and opens no PR, so the implementation lane needs its own card. ⛔ objectui#7759 stays open and unclaimed.

⭐ Director batch #112 delegated this to the seat: 「A 组按 #4580 收尾」 — finish group A against the existing objectui#4580 ruling, ⛔ without a maintainer letter.

The ruling, and the face that already obeys it

objectui#4580, revised Q1 ruling, option A widened the label keys to accept an inline locale map. BaseSchema carries it on both faces:

• packages/types/src/base.ts:140 — label?: string | I18nLabel;
• packages/types/src/base.ts:158 — description?: string | I18nLabel;

⇒ the base pair is CLEAN. The three pairs below restate the key as a plain string, so the narrowing is on the declared side and a forward mirror-vs-declaration comparison reads them as clean while an author writing the declared-upstream locale map is refused by tsc.

Premise re-derived on origin/main before filing

pair	key(s)	what the TS face says
app.ts — AppComponentSchema	label	plain string (several sites, incl. :94 label: string;, :385 / :519 label?: string;)
objectql.ts — ObjectGridSchema	label, description	plain string on both
layout.ts — PageNodeSchema	aria (the nested aria label)	per objectui#7759 group A — ⛔ re-derive, this seat did not confirm this one

Firing control that I18nLabel is real and reachable: it occurs 26× in base.ts and 4× in objectql.ts, and 0× in app.ts — so it is an existing, importable symbol already in use in one of the two files, ⛔ not something this card invents.

⚠️ ⛔ Re-derive every address above. The ObjectGridSchema line numbers this seat took came from an awk-extracted block and are offsets within that block, not file lines — a bad probe value, reported as such rather than passed off as a reading. This seat has had card line numbers rot twice tonight (objectui#9026, objectui#8832) and deleted out from under a card once (objectui#8811).

Why this is the protocol direction, not a local widening

The maintainer's principle: 「我们的项目以 objectstack 协议为准」, and being narrower than the protocol is the forbidden direction. The spec declares the locale-map form; objectui's BaseSchema already matches it; these three pairs are narrower than both. ⇒ widening them is restoring protocol fidelity.

⭐ objectui#4580 rests on producer evidence — bridgeListView assigns node.label = spec.label at react/src/spec-bridge/bridges/list-view.ts:180, where ListView.label is the spec's I18nLabel. ⛔ Re-derive that site: if the producer no longer does this, say so, because it is the ruling's factual basis.

What is owed

1. Confirm or refute each of the three pairs, per key, with exact commands. ⭐ Especially PageNodeSchema::aria, which this seat did not verify.
2. Align the declared face to the ruling's form for each confirmed key. ⛔ Do not touch BaseSchema — it is already correct.
3. A firing control per key: an inline locale map must be shown refused by tsc before and accepted after, plus a control key whose behaviour does not move.
4. ⚠️ Check whether each key's zod mirror already accepts the locale map. If a mirror does not, that pair is a different defect in the opposite direction — ⛔ report it, do not silently fix both faces in one stroke.

Clause-②: yes — this moves a published authoring face. ⛔ Declared yes on the charter tie-break (unsure ⇒ yes), ⛔ not because a widening tell fired; the direction here is restoration toward the protocol.

⛔ The maintainer's ordering rule governs this card

Verbatim, from the director's batch #112 note: 「我们的项目以 objectstack 协议为准,文档应该以实际实现为准。协议不正确的应该先修改协议。」 and its ordering gloss: 凡「实现或立 spec 卡退役」处,先判协议对不对;判协议不对的,spec 卡先行、本卡阻塞其上。

⇒ ⛔ Never narrow or widen a spec-declared shape locally in objectui. ⛔ Never add an author-writable key the spec does not declare. If you judge the protocol itself wrong, the deliverable is stop and say so — a spec card goes first and this card blocks on it.

Standing rules — read every line, they are not boilerplate

Identity. The card is assigned and the Claim: on it is yours; it names your branch. ⛔ Never write the assignee field. ⛔ Never post a second Claim:. If the newest Claim: names another branch, stop and report.

Container hazards.

• /home/user/objectui is SHALLOW with a STALE origin/main. ⛔ Never git fetch, git checkout, or cut a worktree there. Clone fresh into your own scratchpad subdirectory.
• /home/user/objectstack is a shared primary checkout — read-only.
• ⛔ Never git stash. ⛔ Never kill a process by name. ⛔ Never mutate node_modules. ⛔ Never touch content/docs/releases/.
• ⛔ These do NOT exist in objectui and are never a red you can wait for: scripts/pm/os-regen-merge.sh, scripts/pm/check-widening-tells.mjs, scripts/pm/check-clause2-carriers.mjs.

Measurement discipline.

• ⛔ Never write "(no output above = clean)" or any unconditional false-clean echo. Print the command and the exit code.
• ⭐ A control is only a control if it is known to fire in the region being tested. ⚠️ Two true negatives are not a reading.
• ⛔ A bad probe value is not a reading — a multi-line grep -F pattern is split into OR'd patterns and is one. ⛔ An empty gate section is a FAILED RUN.
• ⛔ Never quote a bare grep -c without its exact command.
• ⛔ A claim written in the tree is a claim, not a reading — a docblock, a card body, a triage comment. Three devs refuted this seat tonight by measuring something I had quoted from in-tree prose. Refute me the same way if the measurement says so.
• Read the stored body back after every GitHub write and report what came back.

Deliverable. Worktree → code → tests → changeset → push → draft PR carrying needs:contract-review. ⛔ Do not flip ready, ⛔ do not enqueue, ⛔ no auto-merge — landing is the seat's. Report structured JSON: PR number and head sha, every premise confirmed or refuted with exact commands, your firing controls, and CI as total / success / skipped / non-green plus whether the reported total_count equals the returned array length.

---

Generated by Claude Code

[os-warren]

Claim: session session_01Jmxdo7bmeqCQHLSfmLVX9w (PM seat domain:spec@objectui) → dev subagent on branch claude/issue-9092-inline-locale-declared-face
Session: session_01Jmxdo7bmeqCQHLSfmLVX9w
Branch: claude/issue-9092-inline-locale-declared-face
Clause-②: yes

Scope: group A of objectui#7759 — align three pairs' declared face to the objectui#4580 inline-locale ruling.

⭐ The declaration is yes because this moves a published authoring face, which is the ground director batch #112 put every mirror-moving proposal at yes on — ⛔ not because a widening tell fired. ⇒ needs:contract-review is now on this card, the dual carrier must AGREE, so hang it on your PR too. An in-seat ceiling-tier review is owed on your final head; ⛔ do not flip ready, ⛔ do not enqueue, ⛔ no auto-merge.

⚠️ The claim comment is the carrier the enqueue gate reads, and its spelling is fixed. scripts/pm/check-clause2-carriers.mjs:751-752 requires a line BEGINNING Claim:, and the declaration must be exactly Clause-②: yes or Clause-②: no, unadorned, on its own line. This seat broke that earlier tonight by writing **Claim:** and Clause-②: **yes** — markdown emphasis on a field a machine reads is corruption, and the gate then reported not "this is wrong" but "there is nothing here to read". Recorded so it is not repeated.

⛔ Re-derive every line address on this card before touching anything. Tonight this seat has had card addresses rot twice (objectui#9026, objectui#8832), deleted out from under a card once (objectui#8811), and quoted one bad probe value into a card body (this card's own ObjectGridSchema offsets, flagged in place).

---

Generated by Claude Code

[os-warren]

WITHDRAWN — claim released, card stays OPEN and unassigned. The seat is winding down for the night at the maintainer's instruction; this card is Clause-②: yes, so it owes a ceiling-tier contract review, and starting that now is the most expensive thing left on the board. ⛔ Nothing about the card's premise changed.

No PR was opened and no branch carries work. The run was stopped just as it reached the producer-evidence re-derivation (item 5), so ⛔ no item on this card has been confirmed by a dev — including the two caveats the card already carries: PageNodeSchema::aria was never verified by this seat, and the ObjectGridSchema line numbers in the card body are awk-block offsets, ⛔ not file lines.

---

Generated by Claude Code

[os-litant]

Triage: half-state healed — pm:queue added; priority:p2; type set to Bug. domain:spec unchanged.

分诊席 · session_017VGfRocA8VjczSe84fgjY3 · R+177 · 2026-09-11T02:3xZ · 本评论来自分诊座位

Why it was a half-state, and why the heal is straightforward

The seat wound down at the maintainer's instruction and released the claim cleanly (「WITHDRAWN — claim released, card stays OPEN and unassigned」) — ✅ the right shape, and the assignee came off. ⚠️ But no pm-state went on in the same write, so the card has been sitting in the ③ 析取 (domain:* without a pm-state) and is invisible to every queue. ⇒ 「离手恒走释放…去向 = 新标签态或车道」: the release needed a destination state, and pm:queue is it.

⛔ needs:contract-review is kept: a card-side needs:contract-review before the PR exists is a legal intermediate state, ⛔ not a half-write, and this seat does not hang or clear it either way.

Why Bug and not enhancement

⚠️ The enhancement label is the filer's shorthand and is left alone; the type field is triage's write and the 判据 is 「违背已声明契约 ⇒ Bug」.

objectui#4580's revised Q1 ruling (option A) widened the label keys to accept an inline locale map, and BaseSchema already obeys it on both faces — packages/types/src/base.ts:140 label?: string | I18nLabel;, :158 description?: string | I18nLabel;. The three pairs in this card restate the key as a plain string.

⇒ ⭐ this is not a proposal to widen anything. A maintainer ruling widened it, one face implemented it, three did not, and 「an author writing the declared-upstream locale map is refused by tsc」. ⇒ a landed contract, contradicted by the declared face. Bug.

Why p2

⛔ Not p1 — no runtime is wrong and nothing is mis-rendered; the protocol accepts the locale map, so the value works at run time. The block is at authoring time, in the type face.
⛔ Not p3 — an author following the published ruling is refused by the compiler, which is the most expensive way to be told "no": it reads as the platform not supporting a feature it does support, and the natural next move is to work around it by dropping i18n.

⇒ ⭐ And the narrowing is on the declared side, so a forward mirror-vs-declaration comparison reads these three as clean — the defect is invisible to the instrument most likely to be pointed at it.

⛔ Fences

• ⭐ A ruling is already in hand — director batch chore(deps): bump express and @types/express #112: 「A 组按 finding(types): two competing SchemaNode declarations — core's interface vs types' union #4580 收尾」. ⇒ ⛔ this needs no maintainer letter and ⛔ must not be re-escalated; it is execution against objectui#4580.
• ⛔ Do not widen beyond the three pairs, and ⛔ do not touch BaseSchema — it is the face that is already correct and is the reference.
• ⚠️ The third row is explicitly unconfirmed by the filer: layout.ts — PageNodeSchema aria, carried from objectui#7759 group A with 「⛔ re-derive, this seat did not confirm this one」. ⇒ re-derive it first; if it is already clean, say so and deliver two pairs. ⛔ That is not a shortfall.
• ⛔ Do not close objectui#7759 — its charter is measurement-and-proposal and it stays open and unclaimed.

Size/model suggestion: S — three declarations widened to an existing union, plus the aria re-derivation and a test that the locale map typechecks on each face.

_{分诊席位 · session_017VGfRocA8VjczSe84fgjY3 · R+177 · 2026-09-11T02:3xZ · 本评论来自分诊座位}

---

Generated by Claude Code