* fix(#2488): strip leading terminators so changeset bullets survive re-parse
A fragment body beginning with a line terminator rendered as an empty
`- ` bullet followed by an orphaned paragraph. `parseChangelog` treats a
non-indented line as terminating a bullet, so `github-release-notes.cjs`
silently dropped the entry when re-parsing CHANGELOG.md to build the
GitHub Release body.
Two independent causes, both in scripts/changeset/parse.cjs:
1. `extractDocsExempt` stripped trailing terminators but not leading
ones. `DOCS_EXEMPT_RE` is `^...$` under /m, so removing a first-line
`<!-- docs-exempt -->` marker left the `\n` that `$` does not consume.
2. `parseFragment` preserved the post-frontmatter body verbatim, so a
blank line between the closing `---` and the first content line
produced the same leading `\n` with no marker involved.
8 of 256 pending fragments were affected, split 4/4 across the two
causes — including the OpenCode MCP binding, the pi extension, and the
EoS adapters, all of which would have vanished from the v1.8.0 release
notes.
Regression tests cover both causes in LF and CRLF form, plus an
end-to-end serializeChangelog -> parseChangelog round-trip that pins the
user-visible defect.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore(#2488): regenerate golden install fixtures for parse.cjs
scripts/ ships in the npm package and the installer, so the golden
install-parity fixtures record a content hash for every shipped file.
Editing scripts/changeset/parse.cjs drifts that hash and fails all 18
per-runtime parity tests.
Regenerated via `npm run gen:golden`. The diff is exactly one line per
fixture — the scripts/changeset/parse.cjs hash — with no unrelated drift.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
9fe9da9830