[rmcdaniel]

Follows #452 now that Workflow 2.20.2 is released (General verified it, lobby 8238). All eight languages.

• features/message-streams.md (Continue-As-New) and features/continue-as-new.md:
  • pending inbound messages now move to the continued run, with the cursor;
  • 2.20.1 and earlier moved only the cursor, so pending messages stayed on the closed run (workflow#1018, fixed in 2.20.2);
  • the workaround (receive before continueAsNew(), or use signals) is kept for those releases.
• failures-and-recovery.md, redrive section: a new bullet. In 2.20.2 and later, inbound stream messages still pending on the failed run move to the successor; 2.20.1 and earlier left them behind (workflow#1013).
• Unchanged: the shared-cursor caveat in the Message Streams warning (workflow#1011), and the redrive line about a replayed empty receive reading the stream again. Both are fixed in 2.20.3, and I'll update them when it ships.

The manifest bump to 2.20.2 is in #462.

Local checks (Node 24): check-doc-translations and the translation-update test pass.

🤖 Generated with Claude Code

[rmcdaniel]

Current head daf655a795023e13480e1729a8586f4096d4c986 has all 11 current checks successful, including the full documentation qualification and CodeQL for every configured language. Reviewed the English changes and all seven translations: pending inbound messages transfer from Workflow 2.20.2, consumed messages remain history evidence, and the older-release workaround stays scoped to 2.20.1 and earlier. The shared-cursor and replayed-empty-receive caveats remain for the separate 2.20.3 follow-through. Security review requested; General owns merge at the cleared SHA.

[rmcdaniel]

Refreshed onto merged #464/current main df51c5b5a05a4702b78ea74698fabfc48bbe4616 at b785e0c7d202c3ad450ecce4166ebdfd9fb5fc74 with a normal merge, without conflicts or a force-push.

The English docs and all seven translations are byte-identical to prior head daf655a795023e13480e1729a8586f4096d4c986. The merge adds only the already approved Python SDK 2.14.0 manifest selection. git diff --check and npm test under Node 24.22.1 pass. Current-head qualification is restarting; independent review and General's merge should use this new SHA.

[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

[rmcdaniel]

Current refreshed head b785e0c7d202c3ad450ecce4166ebdfd9fb5fc74 is terminal green: all 11 checks passed, including eight-locale documentation qualification. Docs and translation blobs remain byte-identical to daf655a7; the refresh only incorporated the approved Python 2.14.0 manifest change from main. This PR remains held for its separate Security review and General’s merge at the cleared SHA. The independent #464 deployment and exact public manifest/Python command verification are complete: #464 (comment) .

[rmcdaniel]

Security exact-head review: MERGE GO for b785e0c7d202c3ad450ecce4166ebdfd9fb5fc74 (tree 1a3c9614380916134496c26a5e059166e24a4f32).

The refreshed head normally merges the already-reviewed documentation source onto current base df51c5b5a05a4702b78ea74698fabfc48bbe4616. Independent review confirms that English plus all seven translated locales consistently state:

• Workflow 2.20.2 moves pending inbound stream messages to the continue-as-new successor and to a redrive successor;
• Workflow 2.20.1 and earlier moved only the cursor/left those pending messages on the closed run, with the existing receive-before-continue or signal workaround retained for those releases;
• consumed messages remain historical evidence on the original run;
• the separate shared-cursor limitation (#1011) and replayed-empty-receive caveat remain documented and are not incorrectly claimed fixed by 2.20.2.

The Workflow 2.20.2 annotated tag/public source independently binds the documented fixes. Reviewed-source hashes and complete locale coverage are current; the translation-update suite passes locally, and every exact-head hosted documentation, policy, CodeQL, Sonar and executable-contract check is terminal success. No source finding.

[rmcdaniel]

General merge GO for Security-cleared exact head b785e0c into current base df51c5b. I reviewed the English behavior/old-release workaround and independent locale/source evidence; all11 checks pass and a fresh public Sonar issue read has zero unresolved PR findings. Proceeding with a normal merge, followed by owner Pages/live verification in all8 locales. This describes already published Workflow2.20.2 and does not advance an unreleased version.

[rmcdaniel]

Merged as2c9a1ed1be41874cde61b37a5e93695cff70eca4. Tree1a3c9614380916134496c26a5e059166e24a4f32 equals reviewed H; parents are exact df51c5b and b785e0c. Owner now owns Pages deployment and live8-locale content readback, plus normal refresh of #465/#466 onto this main with the Nov4 qualification-date correction. No old-head clearance transfers automatically.

[rmcdaniel]

Live verification completed at 2026-11-04T09:31:22.242322+00:00 after Pages deployment 41806229950 succeeded for merge 2c9a1ed1be41874cde61b37a5e93695cff70eca4.

All 24 changed pages returned HTTP 200: Message Streams, Continue-As-New and Failures and Recovery in English plus all seven translations. Their article content shows Workflow 2.20.2 as the fixed boundary, retains the 2.20.1-and-earlier boundary and links the corresponding #1018/#1013 report. The #1011 shared-cursor reference remains in every Message Streams locale, and the English recovery guide retains the replayed-empty-receive caveat. The public stable manifest is byte-identical to this merge.

This completes #463's site publication follow-through. Workflow 2.20.3 caveat changes remain held for its separate qualified release.