docs(changeset): mark the 11 changesets 18.0.0-next.2 shipped without a CHANGELOG entry

[objectstack-fleet]

Part of #23818

Clause-②: no

What this PR does

This PR gives each of the 11 changesets that 18.0.0-next.2 shipped without a CHANGELOG entry one lead line:

**Shipped in 18.0.0-next.2**, whose CHANGELOG missed this entry (#23818); listed here one prerelease late.

Each line goes right after the changeset's frontmatter. The frontmatter (package names and bump types) is byte-unchanged, and no other sentence is touched.

The basis is the maintainer's ruling, recorded on #23818 as comment 6209999534, verbatim:

那 11 条怎么补记, 怎么简单怎么处理

This is the changeset half of #23818, split out of #23833 by the seat's decision. The other half is #23833, the merge-queue guard. That PR edits a workflow, so it is Tier H and waits for an authorised approval. This half is not governed (0 of 11 paths hit the register). It can land first, so the next.3 Version Packages PR can be refreshed without waiting for the guard. The commit is a cherry-pick of 15f51d126 from #23833, and its git patch-id --stable is identical (36811cbc07).

#23818 stays open after this lands: the guard in #23833 is its other half.

The 11 changesets

23528-exposure-refusal-code, 23609-legacy-org-read-seam, 23610-page-isdefault-template-slots, 23634-stack-datasource-default-refused, 23712-draft-save-d99-address, 23714-unique-violation-arm-relay, 23723-sandbox-unreadable-rejection, 23732-attachment-readable-ids, 23735-reference-deleted-when, 23740-form-section-columns-no-default, console-daeb77fc84dd.

The card's premises were checked in a full-history clone:

• each one's add commit is an ancestor of the next.2 version commit e5136ff10f;
• none is consumed at that commit;
• no ## 18.0.0-next.2 CHANGELOG section names any of them.

How it renders

I ran changeset version in a throwaway full-history clone that was never pushed. The next.3 sections carry the lead line as the first line of 19 entries across 12 packages: spec 5, runtime 3, metadata-protocol 2, and one each in cli, console, driver-sql, metadata-core, metadata, objectql, platform-objects, plugin-hono-server and service-storage. Each entry keeps its original commit hash. packages/spec:

- a69a40a: **Shipped in 18.0.0-next.2**, whose CHANGELOG missed this entry (#23818); listed here one prerelease late.

  feat(spec)!: a page declares nothing the console does not honour — `isDefault: true` is refused off a record page bound to an object, ...

Why 11 lead lines and not one shared changeset. A shared note would render as a separate entry, and only for the packages its frontmatter names. A reader who greps full-width lands on the #23610 entry and would never see it. The lead line travels with each entry, so it is the simplest form that marks every one as shipped in next.2 at the place the reader lands.

The breaking classification is unchanged. check-adr-0087-registration's breakingDeclaration returns the same verdict for all 11 before and after. The four breaking ones (23610, 23634, 23712, 23740) lose only the bang signal, because their summary line moved down one line. Each keeps **BREAKING and/or its Clause-② narrowing arm.

Check Changeset will be red, and should stay red

The foreign-changeset rule (check-empty-changeset.mjs --base) refuses the 11 M rows. This is its DELIBERATE CORRECTION class, whose documented path is "say so on the PR, naming the note and what changed under it, and get it confirmed". In writing:

• The notes: the 11 listed above.
• What changed: one added lead line each. No sentence was removed or reworded.
• The confirmation: the maintainer's ruling above (comment 6209999534 on release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818).

skip-changeset must not be applied: this PR edits pending release notes, which is a release. Check Changeset is not a required context.

After this lands: #23825 (next.3)

#23825 as cut is behind main by two changesets (#23814, #23817). It also renders these 11 without the lead line. Once this PR lands, it will conflict: it moves the 11 files into .changeset/pre/, and this PR edits them in place.

Refresh it once, after this lands: dispatch release.yml with refresh_version_pr: true alone, the fleet relay's refresh stroke. That re-cuts next.3 from the then-current main, so it consumes the 11 with their lead lines plus everything since.

Until #23833 lands, no check refuses a stale queue build. So queue it only with no changeset-bearing PR ahead of it.

Local gates (head af52476f3, base 43567a8fc)

node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 20 families. Each was run with its exit code captured before any pipe.

• 19 exit 0. These include check-adr-0087-registration --base, check-changeset-no-major --base, check:nul-bytes, check:published-files and check:changeset-gate-self-tests.
• 1 exits 1, as expected: check-empty-changeset.mjs --base origin/main, which refuses the 11 M rows (the section above).
• Reconciliation: --ran reports 20 derived, 20 run, 0 NOT-MEASURED.
• Governance: check-governed-merges --branch reports 0 of 11 paths governed, 22 changed lines (+22 / -0).

---

Generated by Claude Code

[objectstack-fleet]

席位核对 · ACCEPT · PR #23835 (draft, head af52476f3, Part of #23818) · domain:devx seat 2 · session_016PVjjuVPte5XEJvaQx1E4t · 2026-10-16T08:11Z

Checked on GitHub and against the sources, not on the report's say-so. This is the changeset half of #23818, split out of #23833 by the seat's patch-round record (6210600098 on #23833).

• Shape:
  • 11 files, +22 / −0, all inside the revised claim's surface (the claim revision on release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818).
  • Not governed: this seat ran check-governed-merges --pr 23835 and it reads 0 of 11 paths.
  • The body opens Part of #23818 and has no closing keyword. The card stays open for fix(release): refuse a Version Packages PR whose queue build lands behind main; mark next.2's 11 missed changesets #23833.
• Content, checked by this seat:
  • The PR has one commit, af52476f3. It is a cherry-pick of round 1's 15f51d126, and the git patch-id --stable of each, run by this seat, is 36811cbc07.
  • Each of the 11 changesets gains one lead line plus a blank line, right after its frontmatter: **Shipped in 18.0.0-next.2**, whose CHANGELOG missed this entry (#23818); listed here one prerelease late. No frontmatter byte changes.
  • This is the maintainer's route, ruled verbatim in 6209999534 on release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818: 「那 11 条怎么补记, 怎么简单怎么处理」.
• Gates:
  • Local, by the dev: 20 derived families, 19 exit 0, --ran 0 NOT-MEASURED.
  • Check Changeset exits 1 on purpose. Its foreign-changeset rule refuses an edit to another PR's changeset, and this PR is that edit. It is not a required context: this seat read the main ruleset, and the required contexts are TypeScript Type Check, Test Core, Build Core, Lint & Repo Gates and Governed Surface Queue Guard.
  • CI on af52476f3, read by this seat: 25 success, 8 roster skips, and 1 failure, Check Changeset, as above. Nothing is still running.
• Landing:
  • In this act the seat readies the PR and arms auto-merge through the relay. It then confirms the merge on origin/main.
  • After that the seat dispatches the relay's release.yml refresh_version_pr stroke, so the Version Packages PR chore: version packages (next) #23825 regenerates from the current main. That pass consumes these 11 changesets and also feat(plugin-audit): sys_activity gains writer-stamped read-rule columns with an idempotent backfill, and the withheld-row rule is a predicate with no SYSTEM pre-scan (ADR-0139 E6) #23814's and fix(spec): four metadata type descriptions Setup shows are plain admin sentences #23817's.
  • Merging chore: version packages (next) #23825 is the maintainer's act.

---

Generated by Claude Code

[objectstack-fleet]

Landed: the 11 next.2 changesets carry their "Shipped in 18.0.0-next.2" lead line · domain:devx seat 2 · session_016PVjjuVPte5XEJvaQx1E4t · 2026-10-16T08:42Z

reading	value
merge	#23835 → 3c080a65c8 on origin/main, merged 2026-10-16T08:40:44Z from the merge queue (queued 2026-10-16T08:13:52Z)
blob identity	all 11 .changeset/*.md blobs on origin/main equal the PR head af52476f3 (11 of 11)
version PR refresh	the seat dispatched release.yml with refresh_version_pr: true in this act: run 38875444505

• What this does. The next Version Packages PR, chore: version packages (next) #23825 as it is being re-cut, lists the 11 changesets 18.0.0-next.2 shipped unlisted under next.3, and each entry opens with the lead line. This is the maintainer's ruling 6209999534 on release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818: 「那 11 条怎么补记, 怎么简单怎么处理」.
• What it does not do. release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818 stays open. Its other half, fix(release): refuse a Version Packages PR whose queue build lands behind main; mark next.2's 11 missed changesets #23833, is being reworked. Instead of a merge-queue refusal, which the seat withdrew in 6211287288 on fix(release): refuse a Version Packages PR whose queue build lands behind main; mark next.2's 11 missed changesets #23833, it becomes an automatic version of this same lead line at every cut.
• Merging chore: version packages (next) #23825 is the maintainer's act.

---

Generated by Claude Code