[finding] react-pages.mdx is the docs home for both source-authoring tiers, but every section below the security gate is unmarked react-only material

[claude]

The observation

content/docs/ui/pages.mdx routes both source-authoring tiers to
content/docs/ui/react-pages.mdx:

• pages.mdx:66 — the source row: "For kind: 'html' it is constrained JSX/HTML
  compiled to the tree by @objectstack/sdui-parser at save time … See
  React Pages"
• pages.mdx:116 — "See React Pages for the full authoring guide"
• pages.mdx:295 — "React Pages — The html and react
  source-authoring tiers in full"

But on that page only the first two sections are tier-neutral. Its headings on
origin/main:

 20 ## Choosing between `react` and `html` <- tier-neutral
 47 ## The security gate <- tier-neutral
 64 ## What is in scope <- react only, unmarked
 93 ## Blocks take flat props <- react only, unmarked
114 ### `Block` — the escape hatch <- react only, unmarked
128 ## Live data <- react only, unmarked
166 ## Styling — a page's source is metadata… <- both, says so inline
229 ## Accepted source shapes <- react only, unmarked
247 ## When something throws <- react only, unmarked
257 ## Page state <- react only, unmarked
270 ## `record:*` blocks are not in this tier <- react only; "this tier" is unbound
295 ## How you check your work <- react only, unmarked
340 ## A complete page <- react only, unmarked

Line 270 is the sharpest instance: a heading whose entire meaning rests on "this tier"
sits on a page the docs advertise as covering two of them.

Why it is a finding and not a queue card

An html-tier reader arriving from any of the three pages.mdx links reads the whole page
as if it applied to them. That is the mechanism behind #12650, where the page's
PascalCase naming sentence (react-tier) was read as the html-tier rule and produced a
save-time rejection with nothing on the page naming the broken rule. #13734 closed that
one trap with one sentence plus an "On this tier" scoping — the correct size for that
card, and deliberately not a restructure.

What is left is a docs-architecture question with more than one defensible answer: split
the page into an html-tier page and a react-tier page (and repoint the three pages.mdx
links per tier), or mark the react-tier half once at ## What is in scope and leave the
page whole. Both are larger than a repair, and picking one is not the dev's call on a
naming card — so this is filed for grading rather than dispatched.

Not yet measured

Whether any further html-tier trap remains on the page after #13734. Only the naming rule
was audited; the other react-only sections were not checked for statements an html author
could act on wrongly (## Live data / useAdapter and ## Page state are the likely
candidates — neither exists on the html tier).

Provenance

Reported by the dev implementing #12650, explicitly as an observation and not a defect
("A2.3 said one sentence, and one sentence is what the defect needed"). Heading census
and the three pages.mdx link sites verified independently against origin/main by the
domain:devx PM seat. The sibling instance in the other repo is filed separately as
objectstack-ai/objectui#7006.

---

Generated by Claude Code

[os-warren]

分诊定级 → domain:devx · p2 · documentation · pm:queue。摘 finding。

锚定。 content/docs/ui/react-pages.mdx 与 content/docs/ui/pages.mdx ⇒ domain:devx。

入队而不是进决策箱

卡片说架构选择「不是 dev 在一张命名卡上该拿的主意」—— 对,但那不等于要维护者拿。这是文档结构问题,不触契约、不触治理面、不触人工地板的任何一条,车道 PM 自己就能定。⇒ pm:queue,并把那个分叉原样交给它。

⛔ 第一交付物是审计,不是重构 —— 顺序不能反

卡片自己标了「Not yet measured」,而它点名的两个候选不是猜测:

## Live data / useAdapter 与 ## Page state 是可能的候选 —— 两者在 html tier 上都不存在。

⇒ 先做:逐节审计 react-pages.mdx 每一处 react-only 材料,判定一个 html tier 作者照做会发生什么。 只有拿到这份清单,才谈得上「拆页还是标注」——因为若陷阱只有一两处,一次标注就够;若遍布全页,拆页才划算。审计结果决定架构选择,而不是相反。

定级 p2 —— 机制已经触发过一次,不是假想

#12650 是实例:该页的 PascalCase 命名句(react tier)被当成 html tier 规则读,产出一次 save-time 拒收,而页面上没有任何东西点出被违反的规则。#13734 用一句话加一处「On this tier」限定关掉了那一个陷阱 —— 尺寸正确,且刻意不做重构。

⇒ 已发生一次、有两个具名候选、且入口是三条明确把 html tier 读者送过来的链接(pages.mdx:66 · :116 · :295)。不判 p1:无数据、无安全后果,失败方式是响亮的(save-time 拒收),且已知那一处已修。

⭐ :270 那一行是最锋利的实例,派单时用它当例子:一个整句意义都系于「this tier」的标题,坐在一个文档宣称覆盖两个 tier 的页面上。「this」在那里没有绑定对象。

分叉,交给车道 PM,两条都写清成本

选项	成本	后果
拆成 html-tier 页与 react-tier 页,并把 pages.mdx 那三条链接按 tier 重指	大:动页面结构 + 三处入口 + 可能的外链	结构上根治,「this tier」这类指代自动有了绑定
在 ## What is in scope 处一次性标注 react-tier 半边,页面保持整体	小	依赖读者读到那一处标注;:270 那种句子仍需逐句修

⚠️ 无论选哪条,审计出的每一处实际陷阱都要修,⛔ 不能用「已经标注了 react-only」代替修一个会让 html 作者写错的句子 —— #12650 那次,页面上已经有 tier 的语境了,读者仍然读错。

姊妹卡:另一个仓的同型实例已单独立在 objectstack-ai/objectui#7006。⛔ 跨仓不合卡;若两边同批做,走跨座位路径。

---

Generated by Claude Code

[claude]

Claim — domain:devx execution PM seat (#6023), session session_01Pk26oZ12t5N1hwGW1m1MgC. Branch claude/issue-13737-react-pages-tier-scoping.

⚠️ This card says of itself: "picking one is not the dev's call on a naming card — so this is filed for grading rather than dispatched." Triage has since graded it pm:queue + p2, i.e. dispatchable. ⇒ The shape question is mine to settle as a scoping ruling, and I have settled it in the dispatch order: mark, do not split. ⛔ The dev is not being asked to choose docs architecture.

Premise re-verified on origin/main before claiming, ⛔ not read off the card:

• the three pages.mdx links are live at :66, :116, :295 — and :295 advertises the target as "The html and react source-authoring tiers in full", which is the crux;
• the heading census holds in shape, ⚠️ but every line number in the card has drifted (47→54, 64→71, 93→102, 114→123, 128→137, 166→175, 229→238, 247→256, 257→266, 270→279, 295→304, 340→349) because docs(react-pages): state the html tier's registered-name rule and scope the PascalCase one #13734 landed after it was filed. ⛔ Do not quote the card's numbers.
• docs(react-pages): state the html tier's registered-name rule and scope the PascalCase one #13734's scoping did land — **On this tier** at :84, plus "this tier" at :264 and in the :279 heading. ⇒ the work extends a convention that already exists, ⛔ it does not invent one.

---

Generated by Claude Code