[objectstack-fleet]

Requested by Steedos · project thread

Closes #25754 (ruling A, comment 6398564883).

What changed

Only the last prose paragraph of .changeset/25610-notify-email-field-recipient.md. It said delivery "lands separately; until it does, a run that reaches such a node fails at the node". #25721 delivered it, and .changeset/25571-notify-email-field-delivery.md ships in the same release. The paragraph now ends "ships in the same release in @objectstack/service-automation." Frontmatter, Clause-②: and Metadata-protocol: are byte-identical.

Landing point

The expected one, .changeset/25610-notify-email-field-recipient.md. The sentence is the changeset's own text, so there is no other producer.

Expected red

Check Changeset stays red by design (#17712 ruling D: correcting a pending release note is a release decision). The maintainer confirms and merges past it. This must land before #25640 (Version Packages) consumes the changeset. #25640 is untouched.

Acceptance notes

No skip-changeset label: the edit changes published CHANGELOG text.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BPTrzMQwkEcdhpQaa8xuRj

[objectstack-fleet]

席位核对

ACCEPT · domain:spec seat 2 · 2026-10-26T07:19Z · head 1ccff6f5009543e16b1e365d27422de222641cca

1. Shape. Draft, base main, Closes #25754 is the first content line and is the only issue number beside a closing keyword. Assignee zhuangjianguo, author objectstack-fleet[bot] (relay). Diff: 1 file, +1/−1. check-governed-merges --pr 25973: NOT governed, 2 changed lines.
2. Premise and ruling. Ruling A (comment 6398564883). Checked sentence by sentence against the card's replacement text; it matches exactly.
   • Before: "… is the messaging service's half and lands separately; until it does, a run that reaches such a node fails at the node."
   • After: "… ships in the same release in @objectstack/service-automation."
   • Frontmatter, Clause-②: yes (widening) and Metadata-protocol: added are untouched (outside the hunk).
3. Gates (check-runs pinned to the head above). 25 success, 13 skipped, 1 failure.
   • The failure is Check Changeset, red by design (finding: random changeset filenames collide silently across parallel agents — a round overwrote a sibling PR's minor changeset and every gate stayed green #17712 ruling D, named in the ruling and the PR body).
   • check-expected-skips --pr 25973 (roster identical to main's tip): 12 of the 13 skips are rostered. Build UI Deps is outside the roster. The job is new in ci.yml since ci(ui-merge): the seven @objectstack packages build once per run and the ui jobs replay them; every ui cache save is bounded #25963, and its if: is the union of the four ui jobs' filters, which skip on this non-ui diff. So this is a roster gap, not this PR's defect.
4. Accepted deviations. No worktree (the thread container already had the platform branch checked out). Local gates NOT MEASURED (no node_modules there); CI ran the families above.
5. Out of scope. None in the diff. The roster gap for Build UI Deps is reported to the maintainer with this round.
6. Landing. Per ruling A the maintainer confirms and merges past Check Changeset, before chore: version packages #25640 (Version Packages). The seat flips the PR to ready and does not enable auto-merge.