runtime: live review selection returns opaque RoutingSelectionError after admitted planning

[sumitake]

During a documentation audit, installed agent-collab 7.0.6 provider-free planning admitted explicit repository-review targets, but live dispatch returned only a terminal RoutingSelectionError, empty decisions/waves, and outer status: ok. No review content or native execution record was returned. No consumed request was replayed.

Version-bound evidence:

• Plugin 7.0.6; runtime 5.0.7; manifest SHA-256 a11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440.
• Wire SHA-256 a675807e0ff5f0544d7cc9d659914ce2dadac9be8efd0fb56635815e5c3e842a.
• Selected installed x86_64 artifact SHA-256 672dd9b2d4d69b34ffe3d8f99a5269b4ce38f43c940bf8627280fd0a0e3b86b0.
• Request shape: one review.repository unit; explicit target; quality_profile=frontier, effort_class=maximum, max_parallel=1, no dependencies; opaque text payload and caller-verified cwd/device/inode.
• Grok plan review: planning selected review.repository:grok:grok/architecture.repository; live request 05fc335e-f2fd-4d70-b447-6138eb5959eb returned the terminal error.
• Separate final documentation review: Zhipu planning request 229a7a3d-3f05-4edb-a1f9-86824f126fa0 selected review.repository:zhipu:opencode/plan.repository; live request ba12a5ee-0c18-41ba-bcbe-6a4eb96ab212 returned the terminal error. Planning used a short scope description; live dispatch carried the materialized documentation diff. This is not an identical-payload reproduction.

Observed terminal diagnostic: {"transport_diagnostics":[{"code":"RoutingSelectionError"}],"decisions":[],"waves":[],"aggregate":{}}.

Expected: a bounded diagnostic explaining which selection/admission condition failed, with the failure scoped to this request. A planning decision is not proof of native availability. The evidence does not establish a provider authentication failure or native invocation, and it does not justify retrying an uncertain attempt. Private payloads, paths, and environment details are intentionally omitted. Please investigate the error-reporting/selection boundary using the exact released contract.

[sumitake]

Source investigation and draft fix: https://github.com/sumitake/agent-collab-workspace/pull/3171 (signed head ac062fa7ada12c96e389bc87065f335d8f1bfd2b).

The public error shape is reproduced with zero provider launches when live executable eligibility is empty. Planning deliberately remains provider-free, so it can admit the same payload without establishing executable availability. The source now retains bounded rejection categories and the pre-dispatch stage, including carrier_executable_unavailable and provider_attempted: false. Untargeted work selects an available admitted carrier in the original request; an explicit target remains bound. No provider fallback or replay was introduced.

This proves one cause of the reported signature, not the historical incident's unique cause. Payloads, local paths and caller identifiers are excluded from the diagnostic. Focused runtime/routing/process/ACP plus changelog validation passed 327 tests. Native qualification and the signed release remain pending; this issue should stay open until delivered and verified. The separate native-login context observation is tracked in #214 and must not be classified as this pre-dispatch failure.

[sumitake]

Additional installed 7.0.6 / runtime 5.0.7 observation on macOS x86_64. This is additive evidence for the opaque selection diagnostic, not a claim about provider health or the original incident's unique cause.

• Manifest SHA-256: a11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440; wire SHA-256: a675807e0ff5f0544d7cc9d659914ce2dadac9be8efd0fb56635815e5c3e842a.
• One work unit: capability=codegen.repository, explicit_target=grok, frontier/maximum, max_parallel=1, no dependencies, opaque public-source remediation payload, exact device/inode-bound disposable public repository cwd. Only the installed coordinator was invoked through EOF-delimited non-PTY stdin; no raw CLI, outer timeout, fallback or replay.
• Provider-free planning request a2a2e10d-dfad-47d8-9fa4-3439b83f02d6 admitted codegen.repository:grok:grok/codegen.repository.
• Fresh live request 44005a05-d4a4-4dad-b12b-3b6fc9362ca6 returned a terminal with empty decisions/waves and transport_diagnostics=[{"code":"RoutingSelectionError"}]. The shim's outer status was ok; there was no worker response or patch. No cause-specific provider-unavailability claim can be supported from this result.

The call used approved native host execution while retaining the provider's sandbox. The disposable source head was unchanged and the captured diff was empty. The missing implementation and its substantive review findings remain open.

[sumitake]

Resolved in agent-collab 7.0.7 / runtime 5.0.8, delivered by workspace PR #3171 and plugin PR #215.

The reported diagnostic defect is fixed: rejected live selection retains bounded cause-specific categories and the pre-dispatch stage, including carrier_executable_unavailable and provider_attempted: false. Provider-free planning remains an eligibility check. Explicit targets remain bound; untargeted selection considers available admitted carriers within the original request. No provider replay or fallback was added.

Closeout verification: the candidate and released provider_runtime.py are byte-identical; 103 focused routing, carrier/coordinator recovery, and native provenance tests passed again on the release closeout source. The signed release is published and installed runtime activation was verified on ARM and Intel.

Closing the opaque error-reporting defect as completed. This does not establish the unique cause of every historical RoutingSelectionError, nor does it classify the separate Intel native authentication failure as a selection failure; that unresolved observation remains in #214.