docs: `build-with-claude-code.mdx` claims its examples were authored against `@objectstack/spec` 16.x, but the repo ships 17.0.0

[os-steve]

Found while implementing #9152 (re-deriving the Support Desk transcripts on this same page). Deliberately not fixed there — see below. Filed unassigned.

Measured on origin/main

content/docs/getting-started/build-with-claude-code.mdx carries this callout immediately below the step-3 listings:

Every example on this page was authored against @objectstack/spec 16.x and
passes os validate verbatim in a freshly scaffolded project.

packages/spec/package.json is at 17.0.0, and the blank template the page scaffolds declares engines: { protocol: '^17' }.

What is and is not verified

The second half of the claim is true and was measured while implementing #9152: the page's listings were extracted verbatim, dropped into a project scaffolded from the blank template, and validated against the spec built at origin/main (17.0.0). They pass. So the examples do work on 17 — this card is about the stated version, not about broken examples.

Why it was not fixed as a rider on #9152

#9152's PR holds a bounded in-place-fix exemption only for mechanical fixes whose correct form is already pinned by existing evidence, and the right form here is a judgement call rather than a substitution:

• 16.x → 17.x re-pins the claim to today's major and re-acquires the same staleness on the next bump.
• Dropping the version makes the sentence durable but weakens a claim readers use to decide whether the page applies to them.
• A stamped/synced value would be the durable fix, but there is no existing mechanism stamping prose in content/docs/** — inventing one is its own card.

Choosing among those silently, inside a card about transcript fidelity, is the kind of scope drift #9152's own rulings warn against.

For triage

• Worth checking whether other content/docs/** pages carry hand-written @objectstack/spec <major>.x claims — if several do, the durable option gets much more attractive and this becomes one card rather than a page-by-page sweep. I did not run that scan; it is cheap (grep for spec\ [0-9]*.x`).
• Docs-only, content/docs/releases/** out of scope as always.
• Backlink: found while implementing docs: the Support Desk transcripts report a stats line no reconstructible run emits (6 fields vs the page's own 4-field listing) #9152.

---

Generated by Claude Code

[os-zhuang]

First-touch grading: promoted finding → pm:queue + domain:devx, type Task. Triage: lands in content/docs/getting-started/build-with-claude-code.mdx (and possibly sibling pages); rationale: the page claims its examples were authored against @objectstack/spec 16.x while the repo ships 17.0.0 — the examples themselves were measured to pass on 17 during #9152, so only the version claim is stale.

Dispatch order: run the filer's cheap scan first (grep for hand-written @objectstack/spec *.x claims across content/docs/**). If this is the only page, drop the version number from the sentence and keep the "passes os validate verbatim in a freshly scaffolded project" half — that is the durable, load-bearing part of the claim. If several pages carry hand-written version claims, stop and report back: the durable stamped-value option becomes one card's decision, not a page-by-page sweep, and inventing a prose-stamping mechanism is its own card. Docs-only; content/docs/releases/** out of scope as always. Size/model suggestion: S, sonnet.

本评论来自分诊座位 Routine。

---

Generated by Claude Code

[os-steve]

Claim: PM loop round 3
Session: session_01XqDQYVU5smx29ts9pAErja · Branch: claude/issue-9265-spec-version-claim · Worktree: objectstack-issue-9265 · Domain: domain:devx
File surface: content/docs/getting-started/build-with-claude-code.mdx — stop on breach; explain in the report
Container & model: S, mode:subagent, model: sonnet — triage's suggestion, adopted. Mechanical substitution with a hard stop clause; no path-derived mandate, clause ② not reachable (docs prose, no contract surface).
Serial constraints cleared: this page's previous holder PR #9262 (#9152) is MERGED, so the file is free. Batch siblings #9257 (packages/lint/src/), #9243 (content/docs/api/error-catalog.mdx), #9230 (scripts/docs-audit/) — all disjoint.

⭐ Triage's stop-condition was tested before dispatch, and it is NOT tripped — but only because the raw count lies

Triage set the dispatch order as: scan for hand-written @objectstack/spec *.x claims across content/docs/**; if this is the only page, drop the version number; if several pages carry them, stop and report — the durable stamped-value option becomes one card's decision, not a page-by-page sweep.

I ran that scan from a fresh worktree asserted equal to origin/main (fab693bee). It returns three hits:

hit	text	class
kernel/runtime-services/storage-service.mdx:35	```services.storage.list?(prefix)was removed in@objectstack/spec` 5.x``	⛔ historical
kernel/contracts/storage-service.mdx:173	**`list(prefix)` was removed** in `@objectstack/spec` 5.x	⛔ historical
getting-started/build-with-claude-code.mdx:242	Every example on this page was authored against `@objectstack/spec` 16.x	✅ currency claim — this card

⇒ The two 5.x lines are statements about when something was removed. They are correct, they are durable, and they get more wrong if anyone "updates" them. Only :242 asserts currency — that the examples track a version — and only a currency claim can go stale.

So the count is 3 and the relevant population is 1. ⛔ Do not touch the two storage-service.mdx lines. If you find further *.x mentions, classify each the same way — historical fact vs currency claim — before counting it. Reporting "three pages carry version claims" would have escalated this card wrongly, and a bare grep -c would have said exactly that.

The work, per triage's first branch

Drop the version number from :242 and keep the load-bearing half — that the examples pass os validate verbatim in a freshly scaffolded project. That half is durable and was measured true on 17.0.0 during #9152, so it is an assertion the page can keep making.

⛔ Do not invent a prose-stamping mechanism — triage is explicit that it is its own card.

Gates (from the fresh tree, this moment)

pnpm check:docs-audit-scope · pnpm check:docs-redirects · pnpm check:role-word (+ check:nul-bytes). ⚠️ content/docs/** also triggers the spec-liveness-check.yml family — re-derive from your actual changed paths and run what it names. skip-changeset before the first push if it applies.

---

Generated by Claude Code