[objectstack-fleet]

Requested by Elon · project thread

Fixes #25638

Clause-②: no
Metadata-protocol: none

维护者速读(草稿)

• 改了什么: 仓库里 79 份 CHANGELOG 的 18.1.0 段落，每一条改为写它自己的提交号。原来 265 条里有 260 条（另有 6000 行 "Updated dependencies"）写的都是回滚提交 3937697。正文一字未动，只换提交号。
• 为什么改: 读者要顺着提交号找到每条改动。生成器的修复已在 fix(release): a changeset a revert restored is credited to the commit that first added it in the CHANGELOG #25669 合入，以后再切版不会犯；这个 PR 补正已经发布的 18.1.0 文本。
• 风险与代价（含回滚）: 只改 CHANGELOG 文本，不碰代码和 npm 上已发布的包，也不重发 18.1.0。下一次发版的包会带上更正后的 CHANGELOG。回滚 = revert 本 PR。
• 席位意见: （席位填写）
• 你要做的: 改动 12,812 行，超过 3000 行的人工合并线，需要你亲手合并。

What changes

The 18.1.0 sections of 79 CHANGELOGs, 74 under packages/ and 5 under examples/. Each entry and each - Updated dependencies [...] line now names the commit that first added its changeset, not 3937697, the #25605 revert that re-added 260 changesets before the re-cut (#25606, e649c2d91e). Nothing else in any file moves.

How it was produced (regenerated, not hand-edited)

• I checked out e649c2d91e^ (8801f2bb37, the tree chore: version packages #25606 cut) with main's generator from fix(release): a changeset a revert restored is credited to the commit that first added it in the CHANGELOG #25669 (scripts/changeset-changelog.mjs, scripts/release-pending-publish.mjs, .changeset/config.json). I ran the root version script's first two steps there, release-pending-publish.mjs annotate-shipped then changeset version, and copied the 79 CHANGELOGs it moved.
• main has not touched any CHANGELOG since e649c2d91e (git log e649c2d91e..origin/main -- '*CHANGELOG.md' is empty), so the copy replaces exactly the published text.

Evidence

• With 7-hex hashes normalised, all 79 files are identical to e649c2d91e. Every changed line differs only in its commit.
• 265 distinct 18.1.0 entries, none naming 3937697.
• The eight Shipped in 18.0.0 entries name 6b9e6df 7cacad5 950f949 9a06f0b abd5acd de9cd1f df8bb40 e5b3de0, exactly the adding commits fix(release): annotate-shipped passes over a reverted cut instead of reading it as the version commit #25607 measured.
• The five changesets merged after the revert keep a57643d 9f39094 4a25192 4395cbc cb38a8c, as at the cut.
• The result is byte-identical to the amendment produced on 2026-10-24 by the same method from fix(release): a changeset a revert restored is credited to the commit that first added it in the CHANGELOG #25669's branch head. That run also re-cut from a depth-1 clone and got byte-identical files.
• The published tarballs are not touched. ⛔ No republish of 18.1.0.
• check:commit-card-trailers --range origin/main..HEAD and check-nul-bytes pass. The dispatch-gates --commands run is reported on the card.

Tier and surface

• 12,812 changed lines, all in **/CHANGELOG.md. That is over 3000, so this needs the maintainer's own merge. No governed path.

Acceptance notes

• Release-lane finding (for the seat to file): content/docs/releases/v18/18-1.mdx lines 86-91 (docs(releases): 18.1.0 release facts as measured, and the upgrade checklist walked from 18.0.0 #25616) say 260 of 265 entries open with 3937697 and tell readers to search an entry's headline. After this lands, that is true of the published tarballs only. The repository's CHANGELOGs name each entry's own commit. Code PRs do not edit content/docs/releases/, so this needs a docs-only change.

skip-changeset: this amends released text in place (#24912 precedent) and publishes nothing new. A changeset would add an entry about the CHANGELOG itself.

🤖 Generated with Claude Code

https://claude.ai/code/session_01X36HeTaoAfX2pS589N9FYP

[github-actions]

📓 Docs Drift Check

⚠️ 74 changed file(s) yielded no anchor (packages/adapters/hono/CHANGELOG.md, packages/apps/account/CHANGELOG.md, packages/apps/setup/CHANGELOG.md, …), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 74 changed package(s)).

What this run could not see

• 74 changed file(s) yielded no anchor (packages/adapters/hono/CHANGELOG.md, packages/apps/account/CHANGELOG.md, packages/apps/setup/CHANGELOG.md, …) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 175 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json e2a4b6a06315959625748b44ed91b1f9731c67ee → packageMentionDocs.