Uh oh!
There was an error while loading. Please reload this page.
docs: drop stale spec-version claim from build-with-claude-code.mdx - #9286
Merged
Conversation
The page's info callout claimed its examples were "authored against `@objectstack/spec` 16.x" while the repo ships 17.0.0. The examples themselves were measured to pass `os validate` verbatim on 17 during #9152 — only the version claim was stale. Drop the version number and keep the durable, measured-true half of the claim rather than re-pinning to 17.x (which would only reacquire the same staleness on the next major bump). A stamped/synced version value is a separate mechanism this repo does not yet have; inventing one is out of scope here per triage. Two other `@objectstack/spec N.x` mentions in content/docs/ (both in storage-service.mdx) were checked and left untouched — they are historical-removal statements ("was removed in 5.x"), not currency claims, and are correct as written. Part of #9265
os-steve
marked this pull request as ready for review
August 17, 2026 11:45
github-merge-queueBot
removed this pull request from the merge queue due to no response for status checks
Aug 17, 2026
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes#9265
What
content/docs/getting-started/build-with-claude-code.mdxcarried an info calloutclaiming its examples were "authored against
@objectstack/spec16.x" while therepo ships 17.0.0. The examples themselves were measured to pass
os validateverbatim on 17 during #9152 — only the version half of the claim was stale.
Before:
After:
Per triage (issue comment) and Zone 1 rulings: drop the version number rather than
re-pin it to
17.x(which would only reacquire the same staleness on the nextmajor bump), and keep the durable, measured-true half of the claim. Inventing a
prose-stamping mechanism is explicitly out of scope — that is its own card.
Scan for sibling pages (Zone 2 of the dispatch)
Triage's dispatch order was to scan
content/docs/**for hand-written@objectstack/spec *.xclaims first, and stop/report if several pages carry them.Ran that scan fresh from
origin/main(fab693bee) — it returns 3 hits, but only1 is the relevant class:
content/docs/kernel/runtime-services/storage-service.mdx:35services.storage.list?(prefix)was removed in@objectstack/spec5.xcontent/docs/kernel/contracts/storage-service.mdx:173list(prefix)was removed in@objectstack/spec5.xcontent/docs/getting-started/build-with-claude-code.mdx:242@objectstack/spec16.xThe two
storage-service.mdxlines state when something was removed — they arecorrect and durable, and become wrong if "updated". Only the
:242line assertscurrency. So the stop condition (several pages carrying a currency-style version
claim) is not tripped; this PR is the single-page fix triage's first branch called
for.
Scope
Docs-only.
content/docs/releases/**untouched, as always.Tests
Local gates run from a fresh worktree on
origin/main(fab693bee), commitcf4735ef9:pnpm check:docs-audit-scope— passpnpm check:docs-redirects— passpnpm check:role-word— passpnpm check:nul-bytes— passpnpm --filter @objectstack/spec check:liveness— passpnpm --filter @objectstack/spec check:empty-state— passpnpm --filter @objectstack/spec check:variant-docs— passpnpm --filter @objectstack/spec check:strictness-ledger— passDocs-only content change, no user-visible package release — applying
skip-changeset.Generated by Claude Code
Generated by Claude Code