The withdrawn `dist/index.d.ts` byte-identity sentence survives verbatim in five released CHANGELOGs — decide whether released records get amended

[claude]

Found while implementing #5673 (the docstring correction). Filing rather than absorbing:
#5673's fence is the comment carrying the claim, and this half is a question about
released records, which is a ruling rather than an edit.

What is there

The sentence #5673 withdrew from packages/core/src/types/index.ts was also written into
the #4580 changeset, and the release tooling copied that changeset verbatim into every
dependent package's CHANGELOG. Five copies are in the tree today, all identical, all
carrying the last sentence:

Core's entry surface is unchanged: dist/index.d.ts is byte-identical across the change.

packages/components/CHANGELOG.md:1472
packages/core/CHANGELOG.md:1021
packages/plugin-dashboard/CHANGELOG.md:581
packages/react/CHANGELOG.md:450
packages/types/CHANGELOG.md:705

Search scope: git grep -nI over all 5001 tracked files, patterns index\.d\.ts
(144 hits), byte.identical, entry (type )?surface, and the exact sentence. Control:
is byte-identical across the change — a phrase known present — returned six files
(the five above plus one unrelated i18n test), searched the same way; a
known-absent control string returned exit 1 with zero lines, so an empty result is
distinguishable from a broken search.

Why it is not just noise

The measurement is vacuous for the reason #5673 records: core/dist/index.d.ts is
emitted from a barrel that only forwards the symbol, so it is byte-identical under any
change to a re-exported declaration's shape — measured again in #5673's PR with a probe
that moved the declaring module's .d.ts and left both core files unmoved. A reader who
finds the claim in a CHANGELOG has no way to know it was withdrawn.

Why #5673's PR did not rewrite them

Stated so the decision is made on purpose rather than by omission:

1. They are release records for a shipped release, and the same text is already published
   to npm on five packages. A repo-side edit cannot recall what shipped; it only makes the
   repo disagree with it.
2. This repo composes CHANGELOGs from .changeset/*.md at release time. Hand-editing the
   compiled artifact is off that path.
3. It is a five-file diff on append-heavy files, outside the card's fence.

Options

• A — leave them, and let the source docstring carry the correction. Cheapest;
  accepts that a reader of the release notes sees the withdrawn claim.
• B — append a one-line correction to each of the five entries, pointing at [finding] #4580's "dist/index.d.ts is byte-identical" justification is a vacuous measurement, and it is written into the repo as evidence #5673.
  Keeps history readable and marks it corrected; five-file diff, and it edits compiled
  release notes.
• C — record the correction once somewhere durable (e.g. the header of
  scripts/check-changeset-presence.mjs, where this repo already keeps findings of this
  shape) and leave the five entries alone.

No recommendation offered — the trade is "accuracy of a released record" against "release
notes are compiled, not edited", and that is a maintainer call.

Filed unassigned.

---

Generated by Claude Code

[claude]

分诊落箱(session session_01Kktexqp6uVuFMztvvTMf3V,2026-08-24)。一句话问题:一句后来被撤回的技术断言,原样留在五份已发布的更新日志里 —— 要不要去改已经发出去的历史记录。

选项 × 真实代价:

• A. 不改,关卡:源头注释已由 [finding] #4580's "dist/index.d.ts is byte-identical" justification is a vacuous measurement, and it is written into the repo as evidence #5673 纠正;发布记录如实保留「当时怎么认为」。业务上 = 更新日志继续可信为「发布当时的记录」,无人被它引导做任何动作。
• B. 逐行授权加更正注:照 #9734 先例,五处各加一行「post-publication correction」。代价:动 append-only 记录五处,先例扩大;业务上 = 读旧日志的人多一行提示。

四棱:① 长远:append-only 纪律本身比这句话值钱 —— #9734 的授权是针对「教读者跑一条不存在的命令」的活害,本句是历史性描述,无活害,先例不应扩大。② 业务拉动:零 —— 没有客户会因这句旧断言做出任何错误动作(它描述的是当时的构建产物对比)。③ 防 AI:批量改 CHANGELOG 正是 #9734 裁决点名的错误工具;A 让「历史记录不许碰」保持为简单可教的规则。④ 创业:零拉动的编辑不做。

推荐 A(关卡,not planned,源头修正已足);回退 B。置信缺口:无法测 npm 侧是否有消费者把该句当作现行契约在依赖(byte-identity 承诺若被外部工具断言过,A 的「无活害」前提失效)。回「A」/「B」即可。裁后执行:A ⇒ 关 not planned,理由引本块;B ⇒ 立五行编辑卡带逐行授权引文。

---

Generated by Claude Code

[os-zhuang]

分诊席四维分析(维护者 2026-08-24 点名要求;裁决仍归维护者——立卡人刻意未给推荐)。

os-decision-facets

一句话问题:#5673 撤回的「dist/index.d.ts 字节同一」空洞测量句,原样留在五份已发布的 CHANGELOG 里。改不改已发布的记录?A=不动(源码 docstring 已更正);B=五处各补一行更正注;C=在耐久处(如 check-changeset-presence.mjs 头部,本仓惯例位)记录一次更正,五份原文不动。

① 实际业务需求:零用户影响——npm 上的文本无论如何收不回;风险只是翻旧 release notes 的读者信了一个空洞测量。边际。→ A/C。
② 项目长远合理性:本仓 CHANGELOG 是 changeset 编译产物——手改编译产物偏离发布管线纪律(B 的实质代价);C 在守卫脚本头记一次,既留下更正痕迹又不动管线。→ C。
③ 防 AI 犯错:agent 引用这句话作证据的路径主要是源码 docstring——那里 #5673 已更正;考古路径(翻 CHANGELOG)由 C 的耐久注记兜住。B 只多覆盖"只读 CHANGELOG 不读别处"的窄场景。→ C。
④ 创业阶段不扩散需求:A 零成本,C 一段注释,B 五个 append-heavy 文件的 diff。→ A/C。

推荐:C(四轴同向,A 可接受)。 裁后执行:C ⇒ 一张 S 级机械卡(守卫头部注记 + 指向 #5673),本卡关;A ⇒ 直接关,理由记录在案。本分析看不见什么:您对「已发布记录的事实准确性」的重视程度本身——若您认为发布记录必须逐字可信,B 才是对的,那就接受五文件 diff 的代价。

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling recorded — C: record the correction once, durably; released records stand

Provenance: maintainer, 2026-08-24, live PM chat, verbatim: 「接受你的建议。」 on the aligned four-facet analysis above.

Ruled: the five released CHANGELOG entries are not edited (compiled release artifacts stay on the changeset pipeline; npm copies are immutable anyway). The correction is recorded once in a durable, greppable place: the header of scripts/check-changeset-presence.mjs (this repo's established home for findings of this shape), stating that the #4580 changeset's "dist/index.d.ts is byte-identical" sentence was a vacuous measurement withdrawn by #5673, with the file list so an archaeologist landing on any of the five copies can find the withdrawal.

This card converts to that S-grade mechanical task. State: needs-user-decision → pm:queue (ui lane), type Task — closes via the one-comment-block PR.

---

Generated by Claude Code