[rmcdaniel]

Moves the Unreleased entries under ## 2.28.0 - 2026-11-13 and sets product-train to 2.28.0, as for 2.27.0 (#1119). The section opens with the behavior-change line General asked for, and the #1117 entry is moved to the top of the section. No entry text changes; I checked this with a sorted-line diff against main, which shows only the heading and the four-line preamble as additions.

Contents:

• Record an outcome for activities, timers and select() losers still open when a run closes #1117 (Settle a run's open activities and timers when its own code closes it (#1117) #1121): behavior change. A run that completes, fails or continues as new cancels the activities and timers it never awaited, such as select() losers, in the closing transaction (cancellation_reason: run_closed). Late claims and outcomes are refused with run_closed, and replay ignores these cancellations. Service-mode cancellation_policy: abandon keeps running, with abandoned_activities on the terminal event and no outcome recorded.
• Record an outcome for activities, timers and select() losers still open when a run closes #1117 follow-up (Close a closed run's expired activity rows instead of re-sweeping them (#1117) #1124): the deadline sweep closes a closed run's expired open rows, without history, instead of re-selecting them forever.
• Cache workflow-code send candidates per identity during an execution #1014 (Load a send identity's candidates once per execution (#1014) #1125): a send identity's candidates are loaded once per execution, so N identical sends in a replay cost one query.

No migration. After merge, a GitHub release 2.28.0 on the merge commit triggers release verification. Then docs#526 (2.28 adoption plus the select() and continue-as-new guide lines) leaves draft.

🤖 Generated with Claude Code

[rmcdaniel]

Security PASS at b762482, on green CI (7 checks were still pending when I looked).

• Metadata only: composer.json product-train 2.27.0 → 2.28.0, plus the CHANGELOG heading and preamble. The #1014 and #1117 follow-up entries are moved, not changed, and there are no code changes.
• Release contents: main's first-parent history from the 2.27.0 tag (6a0aa6f) to a7a836f is exactly four merges: Settle a run's open activities and timers when its own code closes it (#1117) #1121, Close a closed run's expired activity rows instead of re-sweeping them (#1117) #1124, Agree the deadline-triggered cleanup contract (#863) #1122 (docs) and Load a send identity's candidates once per execution (#1014) #1125, all at the heads I passed. Nothing reached main outside a reviewed PR.
• Preamble: it states the behavior change plainly. An un-awaited select() loser is cancelled at close, and abandon is the only way to keep a service-mode activity running, with its outcome never recorded.

After tagging, I'll check that the tag points at the merge commit, that the tree equals this head plus main, and that release verification passed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud