Codex Desktop macOS: delegated Central follow-up loses selected capability roots and completes without tool dispatch

Observed

Direct userMessage: 12 cua_repl.js calls. Delegated functionCallOutput via send_message_to_thread: selected_capability_root_count=0, tool items=0, no lifecycle or batch dispatch.

Expected

A supported continuation mechanism preserves required owner capabilities or documents a root-capable alternative.

Minimal reproduction

Start an owner thread with CUA capability; compare a direct userMessage continuation and a send_message_to_thread continuation; inspect delivery type, selected capability roots, and tool items.

Environment

Codex Desktop 26.901.51231; Codex Framework 152.0.7977.83; macOS 26.6.2 (25G83).

Impact

The production workflow is blocked before any transaction. DOCSWAVE auth is separately healthy (200); active transaction is 0; lock is NONE; Registry and checkpoint were not changed.

Questions

1. Is there an official programmatic root/direct userMessage continuation entrypoint for the same thread?
2. Is loss of selected capability roots for delegated functionCallOutput intended behavior?
3. Is there a supported capability-selection or inheritance mechanism for delegated CUA/MCP turns?
4. What is the official path for continuing an existing root-capable workflow from scheduled automation?
5. Is selected_capability_root_count=0 a known issue in this build?
6. Is an automation restore ACK that renders a card without a persisted ID/readback a known issue?

Notes

No policy/server-regression assertion. Repeated delegated retries, automation restore/create retries, and local capability injection were intentionally suppressed.

Sanitized incident: DOCSWAVE-ROUTING-20260907-01. No credentials, cookies, tokens, OAuth codes, or company document contents are included.

Reproduce the owner-thread comparison using the direct userMessage and send_message_to_thread continuation entry points, then inspect delivery type, selected capability roots, tool items, and lifecycle or batch dispatch. Done means determining whether delegated continuation should preserve root capabilities and either identifying a supported root-capable path or documenting that alternative.