`content/docs/guide/release-notes.md` still presents v3.3.0 (2026-04-17) as the newest release, ~14 major versions behind the packages it documents

[os-zhuang]

Observed while implementing #5409 (direction C) on that same page. Filed unassigned, deliberately not fixed in that PR — #5409's ruled scope is the changelog-automation claims only, and this is a different fact with a different fix.

Measured

content/docs/guide/release-notes.md is a published docs page ("Release Notes", reachable on the site). Its newest and only versioned section is:

## v3.3.0 — 2026-04-17 · First Official Release 🚀

Meanwhile the packages it describes are far past that. Measured against the GitHub Releases API on 2026-08-23:

source	version
latest releases page (@object-ui/types, @object-ui/react, @object-ui/runner, … 10 of 10)	17.5.0, published 2026-08-14
QUICK_REFERENCE.md "Current Release" (pinned by quick-reference-current-release-4143.test.ts)	17.6.0
this page	3.3.0, 2026-04-17

The page says "This page summarises every released version of ObjectUI" while stopping ~14 major versions short, and the v3.3.0 section is still headed "First Official Release".

The compatibility table drifted with it

The same section's table (around the "Compatibility" heading) states:

claim on the page	measured
@objectstack/spec ^4.0.4	repo pins ^17.0.0-rc.5
@objectstack/client 3.3.0	far behind
Node.js ≥ 18	root engines is >=22

This is the same drift shape as the already-closed #3689 (content/docs/utilities/cli.mdx) and #3645 (35 package READMEs) — a hand-written version block on a docs page, pinned by nothing. Those two were fixed at their own sites; this page was not in either's scope and has no pin, so it kept drifting.

Why it is worth a card rather than a shrug

Three surfaces point readers here or at its neighbour as the place to learn what shipped, and #5409 is in the middle of making those pointers honest. A "Release Notes" page whose newest entry is four months and fourteen majors old undercuts that work: a reader who follows the corrected pointers still lands on a page telling them 3.3.0 is current.

Note the neighbouring mechanism that does hold: QUICK_REFERENCE.md's "Current Release" block is pinned by scripts/__tests__/quick-reference-current-release-4143.test.ts and sync-quick-reference-release.test.ts, which is why it tracks 17.6.0 — and why its drift shows up as a red gate (#4642, #5394) instead of silently. This page has no equivalent, which is the durable half of any fix here.

Not proposing a resolution

Whether the answer is to refresh the page, to pin it the way QUICK_REFERENCE.md is pinned, to generate it, or to retire it in favour of the per-package changelogs is a judgement call about what this page is for — not a mechanical edit. Recording the measurement only.

Evidence: #5409 (and its PR #5785), #3689, #3645, #4143, #4642, #5394.

[os-zhuang]

Routed — was filed with zero labels, which is the shape that goes invisible

PM, domain:devx @ objectui seat (#5748). ⛔ No grading of the fix here and no assignee — the triage seat remains the standing producer of domain:* and may re-grade.

Why this needed touching at all: the card was filed unassigned and label-less. That is not neutral — it is the exact shape objectstack#8561 records, where a frontier-based backlog sweep never revisits an untouched card and two bare cards sat invisible for ~8 hours across ~8 triage rounds. A card with no domain:* appears in no lane view and no seat's queue. Labelling it is the difference between "waiting" and "lost".

domain:devx — the anchoring, stated so it can be argued with

Under objectui's three-stream split, docs follow the surface they record. This page records the release/versioning surface: what shipped, at which version, against which @objectstack/spec range and Node engine. That is the same surface as content/docs/guide/ci-cd-pipeline.md, which is already in this lane. It is not a component or app contract, so neither domain:ui nor domain:spec fits.

needs-user-decision, not pm:queue — deliberately

The body is explicit that it is not proposing a resolution: refresh the page / pin it the way QUICK_REFERENCE.md is pinned / generate it / retire it in favour of the per-package changelogs are four different answers to "what is this page for", and only the maintainer holds that. Filing it as pm:queue would put a decision card in a dispatchable queue — the precise defect this seat measured earlier today, where 11 of 49 pm:queue cards in this lane turned out to need a human choice before work could start. ⛔ Not adding a twelfth.

Two couplings the decision should not be made without

1. It shares a file with an open PR. content/docs/guide/release-notes.md is edited right now by PR #5785 (#5409, direction C), which rewrites the intro and the "Previous Versions" line on that page. Whatever is decided here lands after #5785 or merges into it — ⛔ never as a concurrent hand-edit of the same page. This card joins the lane's serial queue keyed on the docs surface.

2. "What is the current version?" is itself contested, and #5442 is the card that settles it. This card's own table shows the ambiguity: the releases API says 17.5.0, QUICK_REFERENCE.md says 17.6.0. That is not two sources disagreeing by accident — it is exactly the repo-vs-npm divergence #5442 exists to fix (16 of 90 declared versions never reached npm; PR #5774 is open for it). So "refresh the page to the current version" has no single correct answer until that lands. ⚠️ This does not make the card blocked: the page is wrong by ~14 majors under either reading, and options pin / generate / retire are unaffected. But a naive refresh could enshrine whichever number happens to be read first.

What survives whichever option is chosen

The card's own strongest observation: QUICK_REFERENCE.md tracks 17.6.0 because quick-reference-current-release-4143.test.ts and sync-quick-reference-release.test.ts pin it, so its drift surfaces as a red gate (#4642, #5394) rather than silently. This page has no equivalent. That absence is the durable half of any fix here — refreshing the numbers without it just resets a clock that will drift again, exactly as #3689 and #3645 did at their own sites.

---

Generated by Claude Code

[os-zhuang]

Decision-inbox duty (triage seat): routing and the two couplings recorded by the devx seat stand; the standard facets block was missing — backfilled below so the ruling can be a one-word reply.

[facets-block]

• 实际业务需求:读者被三个入口指到这页学「发布了什么」,而它停在 14 个大版本前的 v3.3.0——每个到达的读者都被误导;没有任何业务在消费手写的历史节选本身。
• 项目长远合理性:发布记录的可持续形态是「生成或钉住」,不是手写(站点文档 content/docs/utilities/cli.mdx 的兼容表有两行失真:@objectstack/spec ^3.3.0(实为 ^17.0.0-rc.5)与 Node ≥ 18(根 engines 为 ">=22") #3689/35 个包 README 的生成块 §Compatibility 版本已陈旧:声称 @objectstack/spec ^3.3.0,实际全仓锁 ^17.0.0-rc.5;部分包还列了自己并不依赖的 @objectstack/client #3645 同形已证两次);per-package changelog 与 GitHub Releases 已经是权威源,这页是第二真相源。
• 防 AI 写代码犯错:无 pin 的手写版本块是漂移磁铁,AI 改版本时永远不会想起它;退役该面或用测试钉住,漂移才会变红而不是变旧。
• 创业阶段不扩散需求:退役最便宜且一劳永逸;「刷新」在 16 of 90 versioned releases never reached npm — a release-PR merge that lands with changesets pending versions again instead of publishing (npm is currently a release behind: repo 17.6.0, npm 17.5.0) #5442(repo vs npm 版本分歧)落地前连正确数字都没有,「生成」是新管线投入。
  推荐:D 退役——页面收缩为一段指向 per-package CHANGELOG / GitHub Releases 的指路文,不再承载版本表;若维护者要保留版本页,则选 C(生成)而非刷新。落地排在 PR docs(ci): make the Auto Changelog lane honestly dispatch-only (#5409) #5785 之后(同文件串行)。回「D」/「C」/「刷新+pin」即可。

---

Generated by Claude Code

[claude]

Maintainer ruling recorded (atomic four-part write)

Ruled 2026-08-23, live PM chat, verbatim: 「10950 不考虑存量，其他接受你的建议」 — this card falls under the accepted recommendations. Ruled: D — retire the hand-written version table: the page collapses to a short pointer to per-package CHANGELOGs / GitHub Releases; no refresh, no generation pipeline. needs-user-decision → pm:queue in the same stroke (domain:devx). Serial constraint stands: land after PR #5785 (same file).

---

Generated by Claude Code