docs(releases): the v16 page and its index entry still say the train is published as 16.0.0-rc.0 — 16.0.0 and 16.1.0 shipped

[os-zhuang]

Found while closing #8882 (the v17 GA page compile). Same defect class, different major — and it is older than the v17 one: it was already false before 17.0.0 shipped, so it is not a consequence of the GA cut.

The stale surfaces

1. content/docs/releases/v16.mdx, the release-status blockquote (currently lines 16-20):

Release status: the 16.0.0 train is currently published as
16.0.0-rc.0. This page describes the 16.0.0 content; section headings say
16.0.0 for brevity.

2. content/docs/releases/index.mdx, the v16 entry (currently line 22) ends (current series: 16.0.0-rc.0).

What actually shipped

tag	published	prerelease
@objectstack/spec@16.0.0	—	false
@objectstack/spec@16.1.0	2026-07-22T01:09:22Z	false

git tag --list '@objectstack/spec@16*' returns exactly 16.0.0, 16.0.0-rc.0, 16.0.0-rc.1, 16.1.0. So the v16 series went GA and then took a minor; it did not stop at rc.0.

Why the index entry is the sharper of the two

index.mdx uses two parenthetical forms, and they encode series state:

• closed series → (final release: 15.1.1), (final release: 14.8.0) — both match their last tag.
• current series → (current series: ...).

v16 is a closed series (v17 is GA as of 2026-08-14) still carrying the current-series form, and carrying a version that is two releases behind its own last tag. After #8882 marks v17 as the current series, v16 is the second entry on that list claiming to be current.

Suggested fix

Two files, one PR, docs-only, skip-changeset:

• index.mdx v16 entry ⇒ (final release: 16.1.0), matching the v15/v14 house style.
• v16.mdx blockquote ⇒ rewritten as shipped, the way docs(releases): v17.0.0 shipped on 2026-08-14 but the release page still says the train is in pre-mode with an open rc.6 window #8882 did for v17. The "section headings say 16.0.0 for brevity" sentence explained a pre-mode convention and can go with it.

Worth checking in the same pass whether the v16 page has any other pre-mode framing the 16.0.0 cut falsified, and whether a Landed since 16.0.0-rc.N window was left open the way v17's rc.6 window was.

Why this was not fixed in #8882

#8882's scope ceiling is content/docs/releases/v17.mdx + content/docs/releases/index.mdx. v16.mdx is outside it, and fixing only the index line would leave the page and its index entry disagreeing with each other — so both belong in one follow-up rather than split across two PRs.

Per AGENTS.md Documentation Guardrails, content/docs/releases/ is release-owned: this needs a dedicated docs-only PR, never a rider on a code change.

---

Generated by Claude Code

[os-project-manager]

Triage: lands in content/docs/releases/v16.mdx + content/docs/releases/index.mdx ⇒ domain:devx, pm:queue, type Task. Rationale: factual staleness on the releases pages with the remedy already precedented by #8882; per the release-notes guardrail this must be a dedicated docs-only PR (never a rider on code), skip-changeset.

Size/model suggestion: S mechanical, sonnet. The two files must land in one PR so the page and its index entry agree.

---

Generated by Claude Code

[os-project-manager]

Claim: PM loop round 2
Session: session_011RB4waLuNbdruCo6X9oobm
Branch: claude/issue-8886-v16-release-status-stale
Worktree: objectstack-issue-8886
Domain: domain:devx
File surface: content/docs/releases/v16.mdx · content/docs/releases/index.mdx — these two and nothing else (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus
Serial constraints cleared: none outstanding. No other card in this lane touches content/docs/releases/**; the seat's hot-file queue carries no claim on either file. #8892 (the gate for this same defect class) is deliberately not dispatched alongside — see sequencing below. The lane's only other in-flight work (#7529 / PR #8902) is in packages/lint + packages/metadata-protocol, disjoint.

Model tier — upgraded from triage's suggestion, with reason

Triage suggested sonnet (5302838248, "S mechanical"). Dispatching at opus. The version-number substitution is mechanical, but the card also asks for prose rewritten as shipped, a judgement about whether other pre-mode framing survived the 16.0.0 cut, and whether a Landed since 16.0.0-rc.N window was left open. That is editorial judgement on a release-owned page, and there is no gate that will catch getting it wrong — the failure mode is a plausible-sounding wrong sentence, which is exactly what the sonnet floor is not for. The suggestion is an input, not a decision; ⛔ not taken here, and this is the reason.

Premise re-check — performed at 2026-08-15T16:12Z on origin/main @ 85f5e78, all four confirmed

card's claim	measured
v16.mdx blockquote still says "currently published as 16.0.0-rc.0"	✅ present, at the stated location
index.mdx v16 entry ends (current series: 16.0.0-rc.0)	✅ line 22, verbatim
v16 actually went GA and took a minor	✅ git tag --list '@objectstack/spec@16*' ⇒ 16.0.0, 16.0.0-rc.0, 16.0.0-rc.1, 16.1.0
v16 is the second entry claiming current-series	✅ line 21 already reads (current series: 17.0.0, released 2026-08-14) — #8882 has landed

House style confirmed on the same read: v15 ⇒ (final release: 15.1.1), v14 ⇒ (final release: 14.8.0).

⚠️ One thing the card's quote omits. The live blockquote carries a trailing clause the card did not reproduce:

(15.1.1 was a small patch on the previous line — better-auth family pinning and auth-plugin init isolation — covered by the v15 page.)

That sentence is still true and is a cross-reference, not pre-mode framing. ⛔ It must survive the rewrite. The card's "the section-headings-say-16.0.0-for-brevity sentence can go" applies to that sentence only.

Sequencing — why #8892 is held back rather than batched

#8892 is the gate that would catch this class ("nothing fails when a GA'd major's release page still describes itself as a pre-release"). If the gate lands while this page is still stale, main goes red — a shared-infrastructure break every lane pays for. So the instance lands first and the gate follows. #8892 stays in the queue until this merges. ⛔ Do not implement any part of #8892 here.

Guardrail — this PR is the sanctioned exception, and it is narrow

content/docs/releases/ is release-owned: release notes are written centrally at release time, and a code PR that edits them is the exact thing that guardrail exists to stop. The sanctioned remedy for a factual error is a dedicated docs-only PR, which is what this is. ⇒ ⛔ Not one byte outside the two named files; ⛔ no code, no changeset content, no rider of any kind. skip-changeset.

⚠️ ⛔ Do not touch v17.mdx. A chore: version packages PR (#8653) is open and a release may be in progress; v17's page was just compiled by #8882 and is not this card's business.

---

Generated by Claude Code