docs(changeset): 25610 notify email-field note says delivery ships in the same release (#25973)

<!-- claude-projects-attribution: {"github_login":"zhuangjianguo"} -->
_Requested by **Steedos** · [project
thread](https://claude.ai/code/project/chan_018ETKaNwMZCNRYD7D8Q9Ubb?thread=cmsg_018ETKaNwMZCNRYD7D8Q9UbbWjYFBwPKy4wWAQDz2ZW8py)_

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.com/claude-code)

https://claude.ai/code/session_01BPTrzMQwkEcdhpQaa8xuRj

Co-authored-by: Claude <noreply@anthropic.com>

Author: objectstack-fleet[bot]

.changeset/25610-notify-email-field-recipient.md

@@ -22,7 +22,7 @@ A `notify` node's `recipients` takes a fourth form, as the whole value: `{ email
 - The form is the whole `recipients` value, never a list entry.
 - `@objectstack/lint` refuses, at `os validate`, `os lint`, `os build` and the runtime publish door for a flow, an email-field recipient whose field the trigger object does not declare (`notify-email-field-unknown`), one whose field is not `email`-typed (`notify-email-field-not-email`), and one in a flow that hands its run no record of a known object — a schedule, an inbound api call, a record trigger that names no object (`notify-email-field-no-trigger-record`). A trigger object another package declares is not judged.
 
-This change is the protocol half. Delivery — resolving the field to an address, the outbound mail configuration, the per-address rate limit and the messaging-log entry — is the messaging service's half and lands separately; until it does, a run that reaches such a node fails at the node.
+This change is the protocol half. Delivery — resolving the field to an address, the outbound mail configuration, the per-address rate limit and the messaging-log entry — ships in the same release in `@objectstack/service-automation`.
 
 Clause-②: yes (widening)