Repository navigation
content/docs 三处版本宣称失真:architecture-overview 的 @objectstack/spec ^4.0.x(差 13 个大版本)与 architecture.md 的 TypeScript 5.0+ #3708
Description
Blocked-by: #3711
在 #3697 的门禁落地过程中全量测量 content/docs + packages/*/README.md 时量到的,与 #3697 本身(测试-only)不同面,故另立。
事实
| 位置 | 文档写的 | 仓库真相 | 差距 |
|---|---|---|---|
content/docs/guide/architecture-overview.md:16 |
Layer 1: @objectstack/spec ^4.0.4(三层架构 ASCII 图内) |
29 个 packages/*/package.json 全部 ^17.0.0-rc.5 |
13 个大版本 |
content/docs/guide/architecture-overview.md:35 |
consumed as `@objectstack/spec ^4.0.0` (散文) |
同上 | 13 个大版本 |
content/docs/guide/architecture.md:317 |
built with **TypeScript 5.0+** in strict mode |
全仓 34 处 typescript 声明均为 ^6.0.3 |
1 个大版本 |
复核命令:
$ grep -rhoE '"@objectstack/spec": *"[^"]*"' packages/*/package.json | sort | uniq -c
29 "@objectstack/spec": "^17.0.0-rc.5"
$ grep -rhoE '"typescript": *"[^"]*"' package.json packages/*/package.json | sort | uniq -c
34 "typescript": "^6.0.3"
与 #3645 / #3689 同族
PR #3688 删掉 36 个包 README 的 ^3.3.0 生成块,PR #3698 处理了 content/docs/utilities/cli.mdx。这三处是同一族里没被那两次清扫覆盖到的残留 —— 它们不含 ^3.3.0 字面量,所以两次清扫的 grep 判据(^3\.3\.0 / ≥ ?18)都没命中。
:16 落在代码围栏(ASCII 图)内,这也是 #3697 的门禁决定扫描围栏而非照搬 check-doc-links.mjs 的 stripCode() 的实测依据之一。
处置倾向(不替分诊拍板)
按 #3645 / PR #3688 立下的仓规「版本号入散文即漂移保证」,不建议改写成 ^17.0.0-rc.5 / ^6.0.3 —— 重写等于把同一台漂移机器重新上膛。可选:删掉版本号只留包名/工具名,或按 PR #3698 处理 Node 行的办法改指真相位置(packages/*/package.json 的 dependencies、根 package.json)。
门禁现状
#3697 的 PR 已把这三处以 kind: 'stale' 记进 scripts/__tests__/doc-version-claims.test.ts 的清单 —— 记账不清账,债务留在下一个读者会绊到的地方,同时棘轮阻止第十处悄悄加入。本单修好后,必须同步删掉那三条清单条目,否则 ratchet 测试会以「条目所指的宣称已不在树上」变红(这正是它的设计)。
已搜重
architecture-overview spec version、版本 文档 失真 drift docs version 两组关键字搜过开放 issue,除 #3697 自身外无命中。
Generated by Claude Code
Generated by Claude Code
Activity
claude commentedon Aug 7, 2026
Triage:
pm:queue+pm:blocked(Blocked-by: objectstack-ai/objectui#3711). Nodomain:*— objectui is a whole-repo seat and lane labels do not exist here. No transfer to the objectstack backlog either: this is repo-local documentation, not feature-level, not cross-repo, and it touches nopackages/specsurface.Premise re-verified verbatim on
origin/main(fetched at triage time; read at the ref, not in a working tree):origin/mainarchitecture-overview.md:16Layer 1: @objectstack/spec ^4.0.4 (The Protocol)inside the ASCII fencearchitecture-overview.md:35consumed as `@objectstack/spec ^4.0.0`architecture.md:317built with **TypeScript 5.0+** in strict modeBoth counter-readings reproduce exactly: 29 of 29
packages/*/package.jsonpin"@objectstack/spec": "^17.0.0-rc.5", and 34 of 34typescriptdeclarations are"^6.0.3". Uniform on both counts, so there is no "some packages are still on the old major" reading that would rescue the prose.Why blocked, and on the PR rather than the issue.
scripts/__tests__/doc-version-claims.test.tsdoes not exist onorigin/main— it lands with PR #3711 (open, draft, branchclaude/issue-3697-version-claim-gate), where these three sites are already enumerated askind: 'stale'. Landing this fix first would remove three claims the in-flight ratchet is holding entries for, and that ratchet is designed to go red exactly when a listed claim leaves the tree. So the dependency is on the PR, not on the issue: once #3711 merges, this card is dispatchable and its PR must delete the three matching ledger rows in the same change.Direction is already set by repo rule, so nothing is escalated. #3645 / PR #3688 established that a version number in prose is a drift guarantee; rewriting
^4.0.4to^17.0.0-rc.5reloads the same machine. Delete the numbers or repoint at the truth site (packages/*/package.json, rootpackage.json), per the treatment PR #3698 gave the Node line. These three have no in-repo anchor, so unlike #3710 there is no pin-it-down option here.No
target:v17. objectui reaches the release board through the console bundle;content/docsships to the site, not in the bundle. Stale prose in an architecture overview is not something the v17 notes have to apologise for.Duplicate check. Repo-scoped search over open objectui issues for the docs/version/drift shape returns only #3697 (the gate card, correctly a different face — test-only) and this one. #3708 / #3709 / #3710 partition cleanly: unanchored prose here, a wrong scaffold sample in #3709, anchored README restatements in #3710.
本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
yinlianghui commentedon Aug 7, 2026
认领(PM 派发,并卡 #3708+#3709+#3710 三单一 PR — 三者的修复都要清 #3711 门禁 ledger 里各自的 stale 条目,分开派会在同一文件上三重串行)。Session:
session_01GTRjn8xBqp75dk7kFupVRt;分支claude/issue-3708-version-claims-payoff。packages/create-plugin/src/index.ts实际生成的不符(版本错、字段也错) #3709)+ plugin-chatbot/README.md、layout/README.md(两个包 README 的版本宣称与自己的 package.json 不符:plugin-chatbot 的@ai-sdk/reactv3(实为 ^4.0.47)、layout 的 react peer 比清单更宽 #3710)+scripts/__tests__/doc-version-claims.test.ts的 KNOWN_CLAIMS 相应行清除。packages/create-plugin/src/index.ts实际生成的不符(版本错、字段也错) #3709 的脚手架记录按真实生成器输出对齐(truth = create-plugin/src/index.ts:143-153),对齐后按门禁五分类归「清单重述有锚」入 ledger(kind 注明)或改写为无版本形态 — 以该页上下文实测取舍;两个包 README 的版本宣称与自己的 package.json 不符:plugin-chatbot 的@ai-sdk/reactv3(实为 ^4.0.47)、layout 的 react peer 比清单更宽 #3710 两处与自家 package.json 对齐(chatbot 的 ai-sdk 版本、layout 的 react peer 过宽承诺)。@object-ui/plugin-report的 peerDependencies 只允许 React/ReactDOM^18.0.0,其余 28 个 UI 包都是^18.0.0 || ^19.0.0(仓库自身 dev 用 19.2.8) #3690 的 plugin-report 行不碰(方向相反,等其自身裁决)。Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
验收:PR #3726 ACCEPT(三并卡 #3708 + #3709 + #3710,会话
session_01GTRjn8xBqp75dk7kFupVRt,PM 循环)。交付内容:9 处版本宣称逐处清偿(per_claim 处置表见 PR 正文)——有锚族对齐到锚、裸宣称删版本号不改写新版本号(避免"重新上膛");6 文件 +69/−94。doc-version-claims ledger 27→21,stale 9→1(仅剩 plugin-report 一条,已由 #3690 / PR #3727 清偿)。棘轮两步红绿验证完整。
验收方向确认:有锚族对齐而非删除、#3717 欠交付的升级路径(README peer 重述逐字一致断言独立立单)、头注越界的披露理由,三项均成立。dev 新发现已自立 #3715 / #3716 / #3717,进入候派池。
三单随 PR 合并自动关闭(Fixes 三行)。
Generated by Claude Code
Merge branch 'main' into claude/issue-3690-report-peer-widen
docs: 清偿 objectstack-ai#3711 门禁记账里属这三单的 8 处版本失真,并同步收缩 ledger (objects…
test(scripts): doc-version-claims 扫描面加上 skills/,四处脚手架字面量入锚 (objectsta…