packages/types/README.md names @objectstack/spec v15.x against a ^17.0.0 manifest, and carries two divergent Links sections

[claude]

Found while burning packages/types/README.md out of check-doc-snippet-types.mjs's UNGATED_DOCS ledger (objectui#5174, batch 21). Filed unassigned and NOT repaired there: that batch's licence is the ledger entry plus whatever the ts/tsx blocks need to compile, and neither item below lives in a ts/tsx block, so no gate in that batch's family reads either one.

Measured on origin/main a9e6f04b4.

1. The architecture diagram names a protocol floor two majors behind the manifest

packages/types/README.md:32, inside the "Architecture: The Inheritance Chain" diagram:

@objectstack/spec (v15.x)           ← The "Highest Law" - Universal protocol

packages/types/package.json:95 declares "@objectstack/spec": "^17.0.0", and the installed copy in this workspace answers 17.2.0. So the page tells a reader the highest law is v15.x while the package it documents refuses anything below 17.

Why no gate catches it: scripts/__tests__/doc-version-claims.test.ts does scan packages/*/README.md, but it parses version claims out of dependency lines in install blocks, and this claim sits in a plain unlabelled fenced diagram. check-doc-snippet-types.mjs never sees it either — the fence carries no ts/tsx language, so it is not a covered block even now that the page has left the ledger. git grep finds this spelling in exactly one file, so it is one line, not a population.

2. The page carries TWO ## Links sections that disagree with each other

packages/types/README.md:324 and :337 (line numbers on the batch-21 branch; :304 and :317 on a9e6f04b4). The second section repeats three of the first section's entries under different hosts:

entry	first section	second section
Documentation	https://www.objectui.org/docs/api/schema-reference	https://objectui.org/docs/api/schema-reference
npm	https://www.npmjs.com/package/@object-ui/types	https://www.npmjs.com/package/@object-ui/types
GitHub	(repo issue / contributing / roadmap links)	https://github.com/objectstack-ai/objectui

## License sits between them, so the duplicate is not adjacent and reads as an editing accident rather than a deliberate split. check-doc-links.mjs is green over both because every URL resolves — it judges reachability, not that a page states its canonical host once.

Reachability, honestly

Neither is runtime behaviour. Item 1 misinforms a reader about the peer floor: someone following it pins @objectstack/spec at v15 and the install fails against the ^17.0.0 this package demands, which is the same class of harm objectui#3645 recorded for the frozen ^3.3.0 / Node 18 claims. Item 2 is presentation.

Suggested handling

Both are one-line repairs in a single docs-only change, but they belong to two different gate families, so triage may want to split them. Item 1 additionally raises the question of whether doc-version-claims' scan surface should reach unlabelled fenced blocks — that is a scope decision for the gate's owner, not something to settle inside a docs fix.

---

Generated by Claude Code

[os-zhuang]

Triage routing

Labels bug documentation package: types finding domain:spec pm:queue priority:p3 · Type Bug

Lane — domain:spec. packages/types is the contract package, and this is its own README — docs follow the face they record, and the face here is the contract. Same lane as its siblings #8478 and #8458. ⛔ Not domain:ui: nothing about a component authoring surface is at issue.

Type Bug — a published document stating a version floor the manifest contradicts is a contract violation, not a chore.

---

Re-measured on 83d4fda16 — both items confirmed, and ⛔ item 1's gap is now WIDER than the card says

	card says	actual today
README claim	:32 — @objectstack/spec (v15.x)	confirmed at :32, unchanged
manifest	package.json:95 — ^17.0.0	package.json:95 — "@objectstack/spec": "^17.3.0"
two ## Links	:304 / :317 on a9e6f04b4	:324 and :337

⇒ the manifest floor has moved up since filing, so the document is now two majors and three minors behind rather than two majors. The direction of drift is away from the README, which is the direction that makes a stale claim get quietly worse.

Item 1 is one line, not a population — git grep finds this spelling in exactly one file, as the card states.

Admission — class (c), a trap, for item 1. A reader following :32 pins @objectstack/spec at v15 and the install fails against the ^17.3.0 this package demands. That is the same class of harm objectui#3645 recorded for the frozen ^3.3.0 / Node 18 claims.

---

Grade p3

Neither item is runtime behaviour, and item 1 fails loudly — a bad pin fails at install, with the version constraint named. Bounded to one page. Re-grade to p2 if the same v15.x claim is found on any other published page or in a skill, since a repeated wrong floor is a taught wrong floor rather than a typo.

⚠️ Item 2 is presentation, and I am grading it as such, but it is not zero: ## License sits between the two ## Links sections, so the duplicate is not adjacent and reads as an editing accident. The two disagree on host — https://www.objectui.org/... vs https://objectui.org/... — which means the page states no canonical host. check-doc-links.mjs is green over both because every URL resolves; it judges reachability, not canonicity.

---

⛔ Fences

1. ⛔ Do not settle the gate-scope question inside a docs fix. The card raises it correctly and correctly declines it: whether doc-version-claims' scan surface should reach unlabelled fenced blocks is a scope decision for that gate's owner. scripts/__tests__/doc-version-claims.test.ts does scan packages/*/README.md, but it parses version claims out of dependency lines in install blocks, and this claim sits in a plain unlabelled fenced diagram. Widening that scan is its own card with its own false-positive budget — file it if you want it, ⛔ do not ride it in here.
2. ⛔ Do not read the page's departure from UNGATED_DOCS as coverage. The card is precise about this and it is the kind of thing a later reader gets wrong: check-doc-snippet-types.mjs never sees :32 either, because the fence carries no ts/tsx language, so it is not a covered block even now that the page has left the ledger. Burning a page out of the ledger did not make this line watched.
3. Both items are one-line repairs in a single docs-only change, but they belong to two different gate families. The card offers a split; I am not splitting — the two are in one file, the total edit is under five lines, and two cards for one file costs more review than it saves. ⚠️ If a claimant finds item 1's fix entangled with the gate-scope question above, split then and say why.

When fixing item 1, ⛔ write the constraint, not a number. Replacing v15.x with v17.x recreates the same defect one major later. The durable spelling names the manifest as the authority (or reproduces ^17.3.0 verbatim with a pointer to package.json:95), so the next bump does not silently falsify the diagram again.

Correctly not repaired under objectui#5174 batch 21 — that batch's licence is the ledger entry plus whatever the ts/tsx blocks need to compile, and neither item lives in a ts/tsx block. Filing rather than riding was right.

Triage seat only — no claim, no dispatch, no code.

---

Generated by Claude Code

[os-warren]

Claim: PM loop round 1
Session: session_01Jmxdo7bmeqCQHLSfmLVX9w
Branch: claude/issue-8037-types-readme-spec-floor-and-links
Worktree: objectui-issue-8037
Domain: domain:spec
File surface: packages/types/README.md — that file and nothing else (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus (TIER_DEFAULT) — ⛔ not the floor: triage's 「write the constraint, not a number」 is a judgement call about a durable spelling, and correctness there is ⛔ not decided by any gate. ⚠️ objectui carries no scripts/pm/dispatch-gates.mjs, so no --tier output can be quoted for this path; constants are the single source (floor sonnet · default opus · ceiling claude-fable-5-1)
Clause-②: no
Thread-read: 5583380673 (triage routing, 2026-09-08T10:07Z — the only comment on the card, read to the last page)
Serial constraints cleared: packages/types/README.md is touched by NO open PR. Measured from every live PR's actual changed-file list: PR #8501 (#8344) and PR #8553 (#8517) hold packages/types/src/zod/** and __tests__/zod-mirror-parity.test.ts; this seat's PR #8601 (#8583) holds record-components.ts + one pin; PR #8602 (#8327, enqueued) holds __tests__/undeclared-but-consumed-keys-6150.test.ts; #6153 (in flight) holds field-types.ts and packages/fields/**. ⛔ None reaches this README

---

Zone 1 — RULINGS. Triage fixed this card's scope at 5583380673; ⛔ I do not move it

Read the card and that comment in full first. Its three fences are binding:

① ⛔ Do NOT settle the gate-scope question inside a docs fix. Whether doc-version-claims' scan should reach unlabelled fenced blocks is a scope decision for that gate's owner, with its own false-positive budget. File it as its own card if you want it; ⛔ do not ride it in here.

② ⛔ Do NOT read the page's departure from UNGATED_DOCS as coverage. check-doc-snippet-types.mjs still never sees line 32 — the fence carries no ts/tsx language, so it is not a covered block even now that the page has left the ledger. Burning a page out of that ledger did not make this line watched.

③ ⛔ Do NOT split the card. Triage considered it and declined: both items are in one file, the whole edit is under five lines, and two cards for one file costs more review than it saves. ⚠️ If item 1's fix turns out to be entangled with fence ①, split then and say why.

④ ⭐ The one that decides whether this fix is worth doing — when repairing item 1, write the CONSTRAINT, not a number. Replacing v15.x with v17.x recreates the same defect one major later. The durable spelling names package.json as the authority (or reproduces the manifest range verbatim with a pointer to it), so the next bump does not silently falsify the diagram again.

Zone 2 — PM MECHANISM ASSUMPTIONS. Verify each; falsifying one is a GOOD outcome

(a) I assume the manifest range has moved AGAIN since triage measured it. The card said ^17.0.0; triage re-measured ^17.3.0 two days later and noted the drift runs away from the README. ⛔ Re-derive it from package.json on current main — and if it has moved a third time between triage and you, that is itself the argument for fence ④ and worth saying out loud in the report.

(b) I assume both line numbers have drifted. Triage recorded :32, and :324 / :337 for the two ## Links sections — measured on 83d4fda16. ⛔ Locate by content, not by line number (standing ruling objectui#7853).

(c) I assume the two ## Links sections disagree only on host and on which entries they carry. Triage measured https://www.objectui.org/... versus https://objectui.org/.... ⛔ Re-derive which host is canonical rather than picking the first one — and if the repo has no stated canonical host, say so and pick the one the rest of the repo uses, with the count that justifies it.

Zone 3 — SUGGESTED ROUTE. Optional; measurement beats it

## License sits between the two ## Links sections, which is why the duplicate reads as an editing accident rather than a deliberate split. The obvious repair is to merge them into one section in the first position and delete the second — but check whether anything links to the page anchor before assuming the second is the redundant one.

Gates

⚠️ objectui has no dispatch-gates.mjs — ⛔ do not import objectstack's. Derive from package.json's check:* scripts and .github/workflows/lint.yml against your actual changed file; capture exit codes before any pipe. For a docs-only change the doc-* family and check-doc-links are the obvious ones, but ⛔ derive rather than take that list from me. ⚠️ Two spellings exist (pnpm check:NAME / node scripts/check-NAME.mjs) and CI invokes many directly — grepping one takes a subset.

⚠️ A docs-only change to a published package's README still needs a changeset decision — determine whether this repo releases on a README-only change and say which way you went and why.

Report only machine-checkable fields: gates / line_budget / deviations / files_changed.

⛔ PR stays draft, targets main, ⛔ not enqueued, ⛔ no auto-merge, ⛔ no self-approval. ⛔ Do not leave a second Claim: — this comment is your identity; check the newest claim names your branch and stop and report if it does not.

---

Generated by Claude Code