Update roadmap status: #1607 and 6b-1 done, 6b-2 and 7a started

[Paul Lizer (paullizer)]

Summary

This PR updates docs/explanation/features/CHAT_ORCHESTRATION_WORKFLOWS_ROADMAP.md to the state of paullizer-react-v2-ui at 0.261.228 (fd842e1). It changes docs only, in one file: +39/−13 across two commits.

• Status table and summary paragraph.
  • The workflow_results planner capability is done in #1607, v0.261.217. It's behind the same Use Workflow Results In Chat setting as 6a.
  • 6b-1 is done in #1610, v0.261.227. It adds server-side delivery and the status route.
  • Two items are in progress: 6b-2 (the V2 run card, tracker and chat-list indicator) and 7a (the server part of Phase 7's hand-off). 7b, the V2 part, comes after 7a.
  • The status line now reads 2026-10-03 and 0.261.228.
• 6a section. The workflow_results line now describes what Read saved workflow results from chat orchestration (workflow_results) #1607 shipped:
  • one read-only Gather step reads one finished run, either the workflow's latest or the one that finished on a named day in the user's local time
  • the server, not the model, picks the run
  • the result reaches the compose step as fenced, untrusted notes, never as evidence
  • the answer names each run it read
• 6b section. A new "6b-1 done" block records where Phase 6b-1: post workflow results back into chat (server and status route) #1610 differs from, or settles, the plan:
  • The message ID is deterministic: assistant_workflow_delivery_ plus 40 hex characters of a SHA-256 over the run, the chat and the delivery generation. A resumed run therefore posts its own answer.
  • Delivery reopens only when /runtime/resume raises the generation. /resume-failed doesn't trigger it, because it returns 409 for durable runs. An expired record never reopens.
  • Delivery starts from a 256-entry hint queue, with a sweep under the workflow_chat_delivery_sweep lock as the backstop. It makes at most 8 attempts, with backoff from 30 s to 15 min, and stops at expires_at, which is the runtime deadline plus 24 hours.
  • The chat is marked unread before the message is created.
  • A delivered result uses the normal "AI responded" notice. An undeliverable or expired one gets a workflow_chat_delivery notice that links to the classic /workflow-activity page for now. Until 6b-2 lands, the V2 bell labels that notice "Notification".
  • If the workflow was deleted or its runtime control is missing, the delivery closes without a notice. Classic Retry and Edit refuse messages that a workflow run posted.
  • The status route is owner-only: GET /api/v2/orchestration/workflow-runs/status[?conversation_id=].
  • The workflow's own alert rules still fire for the same run (gotcha 55).
  • The 6b introduction now says 6b-2 branches from paullizer-react-v2-ui, since Phase 6b-1: post workflow results back into chat (server and status route) #1610 has merged.
• §9. The 6b decision on how long to keep retrying delivery is marked as settled in Phase 6b-1: post workflow results back into chat (server and status route) #1610.
• Follow-ups. The release-notes integrity count is updated to 164 stale releases at 0.261.228. It was 152 at 0.261.216.

I checked every new claim against the merged feature docs:

• CHAT_WORKFLOW_RESULT_DELIVERY.md: the message ID (L169), the backoff and attempt limit (L118), the hint queue (L399), the sweep lock (L404), the /resume-failed 409 (L427) and the status route (L439)
• CHAT_ORCHESTRATION_WORKFLOW_RESULTS.md: the workflow_results behavior

I didn't change Phase 7's plan bullets or its §9 row. They'll be updated once 7a's plan is approved.

Linked issue

Refs #1543 #1546 #1549

Release Notes & Latest Features

• New Feature
• Bug Fix
• UI Enhancement
• Breaking Change
• Internal only

Is this visible to end users?

• Yes
• No

Is this admin-facing (Admin Settings, governance, deployment, config)?

• Yes
• No

Should this become a Latest Feature card?

• Yes
• No
• Already added

Screenshot needed for the card?

• Yes
• No
• Attached

Version bump

• application/single_app/config.py VERSION third segment bumped, or not needed because this is docs-only
• deployers/version.txt bumped, or not needed because deployers/ was not changed

Testing / validation

I ran each test through its __main__ at ec5f463, with PYTHONPATH=application/single_app;functional_tests:

• python functional_tests/test_docs_app_surface_coverage.py: passed, 7/7.
• python functional_tests/test_docs_site_quality.py: passed, 6/6.
• python functional_tests/test_docs_link_integrity.py: 2/5, the same result as the base. The failures are existing broken links on other pages; none are in this file.
• python functional_tests/test_docs_release_notes_integrity.py: 0/1, also the base result. 164 releases at 0.261.228 aren't on any generated page, and the roadmap's follow-up line now gives that number.
• Outside table rows, no line in the diff is longer than 118 columns. The file still uses CRLF line endings throughout.
• I didn't need to run scripts/build_docs_inventory.py, because no application surface changed.
• I re-fetched paullizer-react-v2-ui before opening this PR. It's still at fd842e1, which is an ancestor of the head.

Documentation

• Release notes updated, or not needed
• Feature documentation updated, or not needed
• Fix documentation updated, or not needed

Security checklist

• New Flask routes include @swagger_route(security=get_auth_security())
• Settings sent to non-admin frontends use sanitize_settings_for_user()
• Browser JavaScript is served from local SimpleChat static assets only; no CDN-hosted JS
• No secrets, keys, connection strings, or local-only artifacts are included