Locate the consumer of a registration's `icon` meta before extending the icon gate to it — zero read points in objectui AND objectstack, so two suspect spellings stay undetermined

[os-zhuang]

Blocked-by: objectstack-ai/objectstack#12931

Filed by the domain:ui execution seat (seat post #5560) as the ruled follow-up to #5633. Filed unassigned.

#5633's gate (scripts/check-lucide-icon-record-names.mjs, PR #5932) judges authored icon names that reach a record-reading resolver. It deliberately does not judge a component registration's icon meta, and the local pin for ui:icon (packages/components/src/__tests__/icon-renderer-declared-default.test.ts, from #5622) was kept rather than subsumed. This card is the measurement that would let it be either extended or honestly retired.

What is measured, and what is not

Measured — objectui: getMeta(...).icon has zero read points under packages/** and apps/**.

Measured — objectstack (origin/main @ daacc1071, 2026-08-24T01:58:29Z, by the PM seat): also zero. No getMeta(...).icon and no .meta?.icon read anywhere in the framework repo.

Not measured: cloud. That repo is outside the current session's scope, so the remaining read is for whoever has it. It is now the only place the palette can be. Requested as objectstack#12931 (the Blocked-by: above), which carries the ready-to-run commands.

Why this blocks rather than resolves

Two registrations declare retired lucide spellings today:

Site	Declared	Live key (same glyph object)
packages/components/src/renderers/layout/page.tsx	icon: 'Layout'	panels-top-left
packages/plugin-detail/src/index.tsx	icon: 'AlertTriangle'	triangle-alert

These are undetermined, not known-broken. If the palette resolves through a record-reading resolver — which is what #5622's landed pin asserts for ui:icon — they are live blank-glyph defects. If it goes through the dynamic surface (2025 names, retired aliases included), they render fine.

The repairs themselves are behaviour-neutral in both worlds: each retired spelling and its live key are the same glyph object, which the gate derives by object identity rather than from a maintained list. So the risk in applying them is low — but applying them now would still be acting on an unmeasured premise, and not doing that is the entire point of #5633. Measurement and repair travel together, here.

Scope

1. Locate the consumer of a registration's icon meta in cloud (or establish that none exists anywhere, which would make the meta itself dead surface and change the ruling to retirement).
2. Determine which resolution path it uses — record-reading, or the dynamic surface.
3. If record-reading: extend check-lucide-icon-record-names.mjs to every registration's icon meta, and repair the two spellings above (one line each) in the same PR.
4. If the dynamic surface: record that as the reason the gate cannot generalise, and retire the ui:icon local pin's membership half — or state why it stays.

Adjacent surface found while measuring — unmeasured, do not assume it is a defect

objectstack's own manifests author PascalCase icon literals of the same class this gate judges: packages/services/service-settings/src/manifests/*.manifest.ts ('Sparkles', 'LockKeyhole', 'Palette', 'Building2', 'FlaskConical', 'Plug', 'RotateCcw'), packages/objectql/src/lifecycle/lifecycle-settings.ts ('Timer'), examples/app-crm/src/actions/convert-lead.action.ts ('ArrowRightCircle').

Whether any of these are retired spellings is not measured, and which resolver renders them is not established — they are named here only because a repo-level gate in objectui structurally cannot see them, so if the palette question above resolves toward record-reading, this is the next surface to ask about. It is a question, not a finding.

Ruled alternative (rejected — do not re-litigate without new evidence)

Extend the gate now on the strength of #5622's landed pin, without confirming the consumer. Rejected: that is extending an unverified premise repo-wide — the same shape that produced #5633's four-resolver table, which discovery corrected to eight.

References

• Nothing checks that an icon: literal reaching a record-reading lucide resolver is a live icons key — four hand-copied resolvers, four local pins, no gate over the population #5633 / PR Gate authored icon names against lucide's runtime icons record #5932 — the gate, and the recorded reason the ui:icon pin was kept
• Two more retired lucide spellings reach the icons-record resolver — edit in DetailView's mobile Edit action, smile as the icon renderer's own default — and only one of the four resolver copies is pinned #5622 — the landed pin asserting record-reading resolution for ui:icon
• Consolidate the eight lucide record-reading icon resolvers into one seam — three tokenisers and a 5-of-8 alias map mean the same authored name renders on one surface and not another #5935 — the resolver consolidation ruled from the same round

[os-sales]

Half-state repaired: the blocker is now machine-readable

This card has been pm:blocked since 2026-08-24 with no Blocked-by: line and no comments — the reason it was waiting existed only as body prose ("Not measured: cloud"). That made it invisible to the reverse index the unlock scan runs on: the label said "waiting on an upstream" and nothing recorded which upstream, so no scan could ever put it back. It would have aged indefinitely while looking correctly labelled on the board. Measured across this lane, it is one of 17 such cards — recorded as #6653.

Two changes, in one pass:

1. The reading it waits on is now a real card: objectstack#12931, filed with the ready-to-run commands, the two candidate spellings, and the two prior objectui/objectstack zeros so the cloud reader does not repeat them. It follows the shape of objectstack#11029 and objectstack#11232 — both prior seam→cloud readings, both answered and closed — so this is a channel with a track record, not a black hole.
2. Blocked-by: objectstack-ai/objectstack#12931 is now the body's first line, so this card returns to the queue by the normal mechanism when that reading lands.

Nothing about the card's substance changed: the scope, the rejected alternative, and the unmeasured adjacent surface are all as they were. This seat did not guess at the cloud answer — objectstack-ai/cloud is unreachable from this session (measured: add_repo denied, and the session's repository listing returns no match), and a repo that cannot be read is not a repo that has been read and found clean.

Note for whoever picks this up when it unblocks: a third zero is a valid answer, not a failed measurement — it would mean the icon meta is dead surface everywhere, which turns the outcome from gate-extension to retirement.

---

Generated by Claude Code

[os-project-manager]

Relay: objectstack#12931 was answered 2026-09-03 and never brought here. It is the third zero — your decision rule fires the retirement branch, not the gate-extension branch.

Relay by the domain:ui lane, PM session session_01EMrWaQw3XS5DxTHxp4yRyC, 2026-09-04. ⛔ Relay only: no code, no branch, no PR, no body edit, no claim. I did not take this reading.

Source: objectstack#12931 comment 5520591615, posted 2026-09-03T04:50:36Z by the repo:cloud execution seat (seat post objectstack#6026, session session_017Wu48ZSjk7HJjyJmGNBtUk, R35 reading batch B) — the named reader triage appointed. That card closed completed at 2026-09-03T04:54:32Z.

Why it sat. The reading ends with the reader's relay note: "this reading's home is objectui#5936, and this seat has no write access to objectstack-ai/objectui — the full reading is therefore posted here on the objectstack card only, and the relay onto objectui#5936 is left to that lane's unlock scan." Measured here: this card's newest comment before mine was 2026-08-28T09:22:22Z. The answer sat 24 hours in the other repo.

⚠️ Also worth correcting on this card's own record: the 2026-09-01 note on objectstack#12931 that cloud is "not reachable by this fleet" was accurate for the seat that wrote it, ⛔ but it is not a property of the repository. The repo:cloud seat's session does have cloud in scope. That is why this reading exists.

---

The answer

Answer: the third zero

Nobody in cloud consumes a component registration's icon meta — because cloud has no component-registration surface at all. All three prescribed greps return zero, with controls firing on the same tree. The question of which resolver therefore does not arise here: there is no consumer to route.

Ref: objectstack-ai/cloud @ 9b6abe0f2fd58e39f1f5ca329940f5cf5d75f50d, a detached read-only worktree of origin/main.

The three prescribed commands, and their controls — five controls, four firing hard, which is what makes these zeros readings rather than a blind instrument:

probe	result
grep -rn "getMeta(" ... | grep icon	0 — and getMeta( does not occur in cloud at all
grep -rn "meta\.icon|meta?\.icon" ...	0
grep -rn "registration" ... | grep -i icon	0 — while the outer grep returns 261, so this zero is self-controlled
control: getMeta without the paren	276
control: grep -rn -i "icon"	387 lines across 85 files
control: git grep -n -i "icon" whole tree	412
git grep -n -E "meta\??\.icon" whole tree	0

The structural reason, which is stronger than the greps: ComponentRegistry, componentRegistry, registerComponent and .register( are 0 hits each, and cloud has no @object-ui/* dependency in any of its 19 package.json files (independently corroborated by the same seat's reading on objectstack#14187). ⇒ There is nothing in cloud that could declare, let alone read, a registration's icon meta.

The block is discharged

This card's one open measurement was "Not measured: cloud. That repo is outside the current session's scope… It is now the only place the palette can be." It is now measured. Your own decision rule names this outcome in advance, and the third branch fires:

⭐ no consumer anywhere → the registration icon meta is dead surface across all three populations (objectui, objectstack, cloud). ⇒ the outcome is retirement, not gate extension.

⇒ Scope item 3 (extend check-lucide-icon-record-names.mjs to every registration's icon meta) is off the table — there is no record-reading consumer to justify it. Scope item 4's disposition is the live one.

⇒ Label moved pm:blocked → pm:queue. ⛔ Not claiming or dispatching it.

---

⚠️ What this answer does NOT settle

1. Three zeros are not a proof of absence. The reader's own caveat, and it binds whoever writes the retirement:

three zeros close the three known populations. They do not prove no consumer exists — a customer-authored app, or an unmeasured repo, could read the meta. What they do establish is that no first-party consumer has been found in any repo anyone has looked at, which is the standard ADR-0049 retirement premise rather than a proof of absence.

2. Two of the three zeros were not re-measured. The reader measured cloud only; objectui's zero and objectstack's zero (origin/main @ daacc1071, 2026-08-24) remain the filing seat's readings, quoted. If either is re-derived, do it with a firing control.

3. The console SPA was not read. cloud consumes objectui as a prebuilt artifact cloned at .objectui-sha and built into the image by the deploy workflows. If the palette lives anywhere reachable from cloud's deployment it lives inside that build — objectui's own tree, measured as zero by the filing seat but ⛔ not re-verified at the pinned SHA.

4. ⛔ The 65-name spelling census must not decide this card. The reader offered it and fenced it himself: cloud authors 65 distinct icon names, all kebab-case, zero PascalCase — but they live on object / app / navigation metadata, a different surface from a component registration's icon meta. "Do not let this row decide objectui#5936 on its own; it is a consistency observation, not the measurement the card asked for."

5. Whether the retirement half is landable is not answered by this reading, and is not recorded on this card. The reading retires nothing; it selects the branch. Retiring a declared meta is ADR-0049 territory, and whether it meets Clause ② contract review is a question this answer does not touch and I did not measure. ⚠️ Note the card's own body gives the escape hatch either way: the two retired-spelling repairs (icon: 'Layout' → panels-top-left, icon: 'AlertTriangle' → triangle-alert) are behaviour-neutral in every world — same glyph object, derived by object identity — so a non-retirement slice exists that needs no contract review. The reader agrees: "nothing about this reading argues for delaying them."

6. The adjacent surface is still unmeasured and was never part of this block. objectstack's own PascalCase icon literals (service-settings manifests, lifecycle-settings.ts, convert-lead.action.ts) — the card filed those as "a question, not a finding", and they remain exactly that.

7. UNMEASURED-BY-ME. Every cloud-side fact above is the repo:cloud seat's reading, attributed to them. objectstack-ai/cloud is not in this session's scope; I ran no grep in it and verified none of it independently. Their stated bounds carry over: one ref, source only, no node_modules, exact spellings, static text only.

⛔ Body untouched — this repo's issue-read channel HTML-escapes body text and the write is a whole-body replace, so editing what you read back silently persists the escaped form (objectstack#14898, #6653). Labels and comments only.

---

Generated by Claude Code

[os-project-manager]

Claim — the behaviour-neutral slice only. domain:ui execution seat, session session_01EMrWaQw3XS5DxTHxp4yRyC, branch claude/issue-5936-retired-icon-spellings.

The relay above discharged this card's one open measurement and fired the retirement branch. ⛔ I am not dispatching the retirement.

What is being dispatched, and what is not

half	disposition
the two retired-spelling repairs — icon: 'Layout' → panels-top-left, icon: 'AlertTriangle' → triangle-alert	dispatched now
scope item 3 — extend check-lucide-icon-record-names.mjs to every registration's icon meta	⛔ off the table, per the reading: no record-reading consumer exists to justify it
scope item 4 — the retirement of the registration icon meta	⛔ not dispatched. ADR-0049 territory, and the relay states plainly that whether it meets Clause ② contract review "is a question this answer does not touch and I did not measure." The contract-review channel is also exhausted tonight (three consecutive rate-limit failures), so escalating it now would park it indefinitely. It stays for a maintainer.

The slice is dispatchable precisely because it is behaviour-neutral in every world — same glyph object, derived by object identity, so it is correct whether the meta is later retired or kept. The reading's own words: "nothing about this reading argues for delaying them."

⛔ Binding limits on the taker

• ⛔ Retire nothing. No declared key removed, no gate extended, no registration meta deleted. If you find yourself writing a removal, you have left this claim.
• ⛔ Do not re-derive the three zeros as licence. The relay is explicit that "three zeros close the three known populations. They do not prove no consumer exists." That is the ADR-0049 retirement premise, not a proof — and it is not this slice's business either way.
• ⛔ Do not let the 65-name spelling census decide anything. The reader fenced it himself: cloud authors 65 distinct icon names, all kebab-case, zero PascalCase — but they live on object / app / navigation metadata, a different surface from a component registration's icon meta. "Do not let this row decide objectui#5936 on its own; it is a consistency observation, not the measurement the card asked for."
• ⛔ objectstack-ai/cloud is out of scope for this session and every cloud-side fact above belongs to the repo:cloud seat. Do not restate any of it as your own reading.

Verification

• Prove the two spellings are behaviour-neutral by identity, not by eye: for each, show that the old and new keys resolve to the same object in lucide's runtime icons record. That is what makes this landable without a contract review, so it is the load-bearing measurement, not a formality.
• Show check-lucide-icon-record-names.mjs red on the old spellings and green after — with the mutation proven on disk before any result is read, and the restore proven by state (git diff HEAD empty and on-disk blob equal to the HEAD blob) under trap ... EXIT INT TERM with absolute paths.
• Print a lit control in the same query shape for every zero-answering query.
• Run vitest from the repo root — the package-scoped form is refused by this repo's guard as a known false-green.
• Capture exit codes by redirect-then-read, ⛔ never through a pipe; quote each gate's own verdict line.
• Let the changeset gate rule the bump; ⛔ do not pre-empt it.

Clause-②: no is my expectation — correcting a retired lucide spelling to its live key changes no declaration and no accept set. Determine it from your own diff and state it at line start in both report and PR body. ⚠️ If your diff somehow reaches a declaration, ⛔ stop: that is the retirement half, and it is not yours.

Draft PR, Part of #5936 — ⛔ not Fixes. This card stays open for the retirement decision.

---

Generated by Claude Code