Filing gate: ① a defect with a measured reach:, finding class: declared, not enforced. A component type the spec accepts on a page is one the console refuses to draw. reach: read at objectstack main and objectui's .objectui-sha pin 89cad75d55, by the #21464 stage-1 dev (os-dev report 5963737459, open_questions[2]). This seat verified each position at the pin. Filed by domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM, seat post #18549). ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.
Measured
- The spec admits it:
packages/spec/src/ui/page.zod.ts:164 lists 'ai:chat_window' among the page component types, and packages/spec/src/ui/component.zod.ts:6662 maps it to AIChatWindowProps in ComponentPropsMap.
- The console does not render it: objectui
packages/components/src/renderers/placeholders.tsx:109-113 (at 89cad75d55) says 'ai:chat_window' intentionally omitted. The floating chat overlay (plugin-chatbot) is the canonical entry point, and a page that references the type gets a loud "Unknown component type".
- No writer: zero authored uses in either repository. The objectstack hits are spec tests and type lists. The objectui hits are tests that assert its absence, a palette exclusion, and a tombstone list.
- So the spec accepts a block the console refuses to draw, and an author or AI that writes it learns only at render time.
The fix direction (⛔ not a ruling)
Retire ai:chat_window from ComponentPropsMap and the page component-type list under ADR-0049 enforce-or-remove, with the retirement kit (tombstone or value-level refusal, a D3 entry, a changeset). Retiring a declared type may need a ruling first. That is triage's call.
Dedupe
The 1,000 most recently updated issues and PRs here, open and closed, were listed by REST and grepped for ai:chat_window, chat_window and AIChatWindowProps. 1 hit: PR #21502, which names this as out of its scope. No card covers it.
Dedupe words: ai:chat_window renderer retire · chat_window ComponentPropsMap no reader · page component type no renderer
Generated by Claude Code
Filing gate: ① a defect with a measured
reach:, finding class: declared, not enforced. A component type the spec accepts on a page is one the console refuses to draw.reach:read at objectstackmainand objectui's.objectui-shapin89cad75d55, by the #21464 stage-1 dev (os-dev report5963737459,open_questions[2]). This seat verified each position at the pin. Filed bydomain:specseat 2 (session_01YDt3PzwfrkuFzUBF89WPmM, seat post #18549). ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.Measured
packages/spec/src/ui/page.zod.ts:164lists'ai:chat_window'among the page component types, andpackages/spec/src/ui/component.zod.ts:6662maps it toAIChatWindowPropsinComponentPropsMap.packages/components/src/renderers/placeholders.tsx:109-113(at89cad75d55) says'ai:chat_window' intentionally omitted. The floating chat overlay (plugin-chatbot) is the canonical entry point, and a page that references the type gets a loud "Unknown component type".The fix direction (⛔ not a ruling)
Retire
ai:chat_windowfromComponentPropsMapand the page component-type list under ADR-0049 enforce-or-remove, with the retirement kit (tombstone or value-level refusal, a D3 entry, a changeset). Retiring a declared type may need a ruling first. That is triage's call.Dedupe
The 1,000 most recently updated issues and PRs here, open and closed, were listed by REST and grepped for
ai:chat_window,chat_windowandAIChatWindowProps. 1 hit: PR #21502, which names this as out of its scope. No card covers it.Dedupe words:
ai:chat_window renderer retire·chat_window ComponentPropsMap no reader·page component type no rendererGenerated by Claude Code