0.1.8 Beta4 gate: Publish the runtime-derived generic Collaboration V2 candidate #284

Parent

#248

Release purpose

Publish 0.1.8-beta.4 after the exact runtime-derived Collaboration V2 lifecycle works on generic Responses routes without V1 corruption or Gateway-owned agent scheduling, the Codex Desktop built-in ImageGen request reaches the authoritative Official image-generation upstream, and rejected POST bodies cannot desynchronize or leak into HTTP parser logs.

Formal maintained-Provider regression across GLM-5.2, K2.7 Code, and DeepSeek V4 Flash 0731 follows in Beta5.

Required inputs

• Previous cumulative release gate: 0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281.
• Exact candidate-bound V2 runtime/wire contract: 0.1.8 Beta4: Reconcile the exact Codex Collaboration V2 runtime/wire contract #392.
• User-owned agent configuration safety: Preserve Codex agents configuration across Gateway overlay lifecycle #199.
• Generic Collaboration V2 implementation and verification: 0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252, 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282, and 0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283.
• Candidate-bound Codex Desktop/Official ImageGen contract capture and pass-through: Beta4: Forward Codex ImageGen requests through the Gateway #401.
• Rejected POST body connection and privacy safety: Beta4: Close or drain rejected POST bodies before connection reuse #402.
• External Provider startup when Official authentication/snapshot is unavailable: Allow Gateway to start with external Providers when Codex sign-in is unavailable #403.
• Provider endpoint Test model-required semantics: Provider endpoint Test misreports a missing probe model as an unsupported endpoint #404.
• Provider model discovery/editor/save/restart state consistency: Provider model discovery remains at 0 and stale editor state can overwrite discovered models #405.
• Closed Beta2 foundations 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64 and 0.1.8 Beta2: Isolate V1 repair from V2 namespace adaptation #198 remain mandatory only as corrected/superseded by the exact 0.1.8 Beta4: Reconcile the exact Codex Collaboration V2 runtime/wire contract #392 contract.

Acceptance criteria

• The exact Beta3.3 candidate lineage and its Chat/history/output-limit regressions are preserved.
• 0.1.8 Beta4: Reconcile the exact Codex Collaboration V2 runtime/wire contract #392, Preserve Codex agents configuration across Gateway overlay lifecycle #199, 0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252, Beta4: Forward Codex ImageGen requests through the Gateway #401, Beta4: Close or drain rejected POST bodies before connection reuse #402, Allow Gateway to start with external Providers when Codex sign-in is unavailable #403, Provider endpoint Test misreports a missing probe model as an unsupported endpoint #404, and Provider model discovery remains at 0 and stale editor state can overwrite discovered models #405 are closed with the required protocol-controlled, UI-contract, and real-client evidence.
• The candidate uses the exact complete V2 Responses collaboration namespace and its six child functions captured in 0.1.8 Beta4: Reconcile the exact Codex Collaboration V2 runtime/wire contract #392; direct/shared function names alone never select V2.
• V1 repair is structurally unable to run on V2.
• Codex Client remains the agent owner/executor; Gateway does not schedule or forge lifecycle state.
• User-owned agent settings survive supported overlay/restart transitions.
• Unknown, conflicting, cross-Home, ambiguous, or unsafe Collaboration state fails before mutation or with one standard terminal failure.
• The candidate-bound Codex Desktop ImageGen request and authoritative Official upstream URL, authentication, request, and response contract are captured without prompts, credentials, or opaque identity.
• POST /v1/images/generations reaches that Official image-generation upstream and returns the response expected by built-in ImageGen; a real candidate-bound Desktop call produces an image.
• ImageGen upstream errors remain upstream errors; there is no Vision Proxy substitution, text-model fallback, Provider/model-name branch, or cross-Provider execution.
• Every rejected POST with a body is safely drained or explicitly closed, produces one intentional response, and cannot emit raw body content through a follow-on parser error/log.
• With no Codex sign-in and no safe Official snapshot, valid external Provider models still start, discover, and route; Official models remain unavailable until a safe snapshot exists.
• Provider Test distinguishes a missing usable probe model from unsupported endpoint protocol, clearly asks for a model, and still auto-uses a discovered model when one is available.
• Discover models immediately updates the active editor, persists discovered and manual models without stale draft overwrite, preserves per-model settings, and survives save, navigation, reselection, and restart; empty/error discovery does not delete existing models.
• Existing task histories are not rewritten or cleaned on disk.
• context_window remains the Codex-facing output limit.
• No model fallback, Provider/model production branch, runtime allowlist, alternate-codec retry, or cross-Provider execution exists.
• Exact candidate SHA review is accepted, CLI/Desktop manual verification is accepted, and the relevant local verification/release gates succeed.
• Only after those gates pass is 0.1.8-beta.4 tagged and published as a manual opt-in prerelease.

Blocked by

• 0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281
• Preserve Codex agents configuration across Gateway overlay lifecycle #199
• 0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252
• Beta4: Forward Codex ImageGen requests through the Gateway #401
• Beta4: Close or drain rejected POST bodies before connection reuse #402
• Allow Gateway to start with external Providers when Codex sign-in is unavailable #403
• Provider endpoint Test misreports a missing probe model as an unsupported endpoint #404
• Provider model discovery remains at 0 and stale editor state can overwrite discovered models #405