Grok 1.0.13 codegen fails closed on one unknown ACP tool event

[sumitake]

Installed plugin: agent-collab 7.0.0
Manifest: 2bf858764510fddfa86f491f677ad1a80d05b854a33d77a9a3230d0cb399fddf
Wire digest: 9ec0c1d0c943a9ba9025dbb554847abea45d5c2dcac893a69ac09539d265a85f

A single managed codegen.repository request targeted logical agent grok at clean workspace head 55b28ed31b3df8d3184a3290d6ceb99b1ee49915 with frontier/maximum and a 600000 ms inactivity lease. The current Grok carrier was 1.0.13 (build 5e9a58528b76), content SHA-256 8669e0fdadceec25b8c159c355f427ffbd82583525d774b6ab1522197ea83b80.

Terminal result: status=protocol_error, error_code=execution_contract_violation, disposition=inspect. Failure trace: adapter_code=provider_error, failure_phase=protocol, tool_outcomes unknown=1 and success/failed/incomplete=0, all operation counts=0, outside_source_observed=false, provider_processes=1, cleanup_confirmed=true. No private_patch artifact or native envelope was returned.

This request was not replayed. The current aggregate unknown-tool treatment appears to reject an otherwise bounded attempt before any repository operation is admitted; diagnostic/format variants should not globally poison execution unless authority, effect, containment, terminal closure, or lifecycle is unresolved. Please retain exact consequence-bearing fail-closed behavior without version- or formatting-coupled allowlists.

[sumitake]

Additive occurrence from the paired 7.0.1 staged release candidate (not installed or published).

• Staged manifest: c9c5b5c01b2531b9e2883fac2bb5ec29f3e3687955c9821748b66f76587ac4b1
• Wire digest: 8932ebcbaea11c4e24e4829256660f5d0f9861f08953a042605146ca82f76130
• Clean workspace head: 593d01afaa8ad49cae3c5c4821b73017f2a4054f
• Request: one codegen.repository, target grok, standard/standard, timeout_ms=600000 as the signed codegen inactivity lease
• Carrier content SHA-256: 8669e0fdadceec25b8c159c355f427ffbd82583525d774b6ab1522197ea83b80 (Grok 1.0.13)

The request remained live past the former five-minute wall-clock bound, then ended terminally as protocol_error / execution_contract_violation; failure phase protocol, adapter code provider_error, tool outcomes unknown=1 with all other outcome and operation counts zero, provider_processes=1, cleanup_confirmed=true, and no native envelope or private patch. No prose was salvaged and the request was not replayed. This reproduces the same unknown-tool failure on the new runtime 5.0.1 candidate while confirming that liveness renewal itself worked.

[sumitake]

Additive evidence from the current Grok managed-route parity repair (installed plugin 7.0.0; no replay):

• request: pr3112-descriptor-codegen, codegen.repository, target grok, standard quality / maximum effort
• exact workspace source head: 92bb109afc50b4721c225a0a2b262bbc5c65da58
• public timeout: 300000 ms, correctly treated by this codegen route as an admitted-progress inactivity lease; the request ran beyond 300 seconds rather than being killed on elapsed time
• terminal result: protocol_error / execution_contract_violation; adapter code provider_error; failure phase protocol
• process facts: provider_processes=1, metadata_process_count=1, cleanup_confirmed=true
• artifact: none; repository reads/search/list=0; one unknown tool outcome
• manifest digest: 2bf858764510fddfa86f491f677ad1a80d05b854a33d77a9a3230d0cb399fddf
• adapter wire: 2146d0bda3cc54ba9e7ed8d35f6ed157a0ed7a9601a71b15095068e57d94e85a
• executable content: 8669e0fdadceec25b8c159c355f427ffbd82583525d774b6ab1522197ea83b80
• implementation fingerprint: eedc77fb54c0213668c88f25bca12868f1d84d6262900e13dbe30c19ef591bfb

The provider-started terminal failure was not replayed. The approved plan was implemented and tested locally by the primary after this unavailable codegen attempt.

[sumitake]

Additive evidence from issue #187 implementation codegen on 2026-08-30 UTC. Installed plugin 7.0.0, manifest 2bf858764510fddfa86f491f677ad1a80d05b854a33d77a9a3230d0cb399fddf, wire 9ec0c1d0c943a9ba9025dbb554847abea45d5c2dcac893a69ac09539d265a85f, coordinator SHA-256 392a63aa74cb3478b334d7a52d3210e94f13c0590648caed13faf3af4fe3b035, Grok executable SHA-256 8669e0fdadceec25b8c159c355f427ffbd82583525d774b6ab1522197ea83b80. Exact request issue187-admitted-progress-codegen-20260830-01 targeted grok codegen.repository/frontier/maximum at clean workspace head d862bcd04edcd5c3381095bee4f21cdc43d24dc4. After roughly nine minutes under the existing codegen progress lease it returned terminal protocol_error/execution_contract_violation: adapter_code provider_error, failure_phase protocol, provider_processes=1, cleanup_confirmed=true, outside_source_observed=false, tool outcomes unknown=1 and all other outcome counts zero. No patch artifact was issued and the request was not replayed.