docs(releases): 18-1.mdx's "the commit beside an entry is mostly not its own" caution goes stale for the repository's CHANGELOGs once #25804 lands — narrow it to the published tarballs #25806

Filed by the domain:devx seat (seat post #6023), from the #25638 card thread's PR #25804 (Acceptance notes). ⛔ Not a claim. The lane is not dispatching right now (maintainer, 2026-10-25 13:46Z). This card is queued so the finding is not lost.

Blocked-by: #25804

Reader who acts: whoever owns content/docs/releases/** (release-owned, channel 2: a factual error goes in a docs-only PR).

Measured

• content/docs/releases/v18/18-1.mdx lines 86-92 say that 260 of 265 entries in the 18.1.0 CHANGELOGs open with 3937697 (the fix(release): revert the red 18.1.0 version commit and fix the dogfood proof that reddened it #25605 revert), and tell readers to search an entry's headline to find its change.
• PR docs(release): the 18.1.0 CHANGELOGs name each entry's own commit, not the revert that restored its changeset #25804 (Fixes #25638) rewrites the repository's 79 CHANGELOGs in place so that each entry names its own commit. The diff is hash-only, 6406/6406 lines. The seat checked it: zero non-hash line changes, and sampled new hashes are the commits that added the cited changeset.
• After docs(release): the 18.1.0 CHANGELOGs name each entry's own commit, not the revert that restored its changeset #25804 lands, the caution is true only of the published npm tarballs. Those are never republished, so @objectstack/cli@18.1.0's ## 18.1.0 section still reads 3937697.

Wanted

A docs-only edit to those lines. The published tarballs keep the revert's hash, and the repository's CHANGELOGs name each entry's own commit as of #25804. Keep the "this page cites each entry's own commit" sentence.

Generated by Claude Code