Uh oh!
There was an error while loading. Please reload this page.
fix(spec): correct stale tags restatements in book.json and liveness README - #9357
Merged
os-steve merged 1 commit intoAug 17, 2026
Merged
Conversation
… book.json and liveness README Same class as #9310/#9317: DocSchema declared `tags` in 17.0.0 (#4509, ADR-0049), making the book `include: { tag }` include variant live, but two more places in the liveness tree still restated the pre-fix claim that the tag rule can never match: - packages/spec/liveness/book.json — the `groups.include` prop's note - packages/spec/liveness/README.md — the `book` row Both corrected to current-state truth, matching the #9317 wording posture and preserving load-bearing cross-references (the #4667 tombstone paragraph on the README row). No verdict change, no behaviour change — ledger prose only. Fixes#9316 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fs18A2DdXLVN2h8PaaFBcP
Contributor
📓 Docs Drift CheckNothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)), so this run has no opinion about the docs. What this run could not see
Coarse fallback — 113 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): |
os-steve
marked this pull request as ready for review
August 17, 2026 16:43
Uh oh!
There was an error while loading. Please reload this page.
os-steve
deleted the
claude/issue-9316-liveness-stale-tags-restatements
branch
August 17, 2026 17:02
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
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#9316
Same class as #9310 (merged as #9317):
DocSchemadeclaredtagsin 17.0.0 (#4509, ADR-0049) — verified today onorigin/mainatpackages/spec/src/system/doc.zod.ts:126,tags: z.array(z.string()).optional(). That made the bookinclude: { tag }variant live (matchesInclude readsdoc.tags,packages/spec/src/system/book.zod.ts:213), but two more places in the liveness tree still restated the pre-fix claim that the tag rule can never match:packages/spec/liveness/book.json— thegroups.includeprop'snote(also bumpedverifiedAtto today, since the claim was re-checked)packages/spec/liveness/README.md— thebookrowBoth corrected to current-state truth, matching the #9317 wording posture (cites #4509/ADR-0049, cross-references the
docside's fuller history) and preserving load-bearing cross-references — the README row keeps its#4667inline-translations-tombstone paragraph intact.No verdict change (
includestaysstatus: "live"), no behaviour change — ledger prose only.Tests
Local gates (worktree
objectstack-issue-9316, heade26f5b14a):pnpm --filter @objectstack/spec run check:liveness— pass (✓ every governed-type property … is classified … the README state table carries a row for each of the 30 governed type(s))pnpm --filter @objectstack/spec run check:empty-state— passpnpm --filter @objectstack/spec run check:strictness-ledger— passpnpm --filter @objectstack/spec run check:variant-docs— passpnpm check:merge-driver— pass (self-test)pnpm check:type-source-resolution— passnode scripts/check-dev-prereqs.mjs --self-test— pass (the full scan half needs a built workspace and is not run by CI on PRs — only its self-test is, perlint.yml)node scripts/docs-audit/check-affected-docs.mjs— passnode scripts/check-nul-bytes.mjs --self-test && node scripts/check-nul-bytes.mjs— passNo changeset — ledger prose only, no user-visible change;
docs/qa/platform-checklist/FOLLOW-UPS.md:83(E1) is an existing append-only decision-register row about the already-merged #9310/#9317 fix (out of this card's file surface, not edited).Generated by Claude Code
Generated by Claude Code