0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252

Activity

1. NOirBRight

   added this to the 0.1.8 — Responses, Chat & CLI stability milestone on Jul 29, 2026
2. NOirBRight

   added

   enhancementNew feature or requestNew feature or request

   ready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent

   wayfinder:taskWayfinder implementation taskWayfinder implementation task

   tier:heavyOrchestrator provider tier: heavyOrchestrator provider tier: heavy

   P1Priority 1: current iteration goalPriority 1: current iteration goal

   on Jul 29, 2026
3. NOirBRight

   marked this as blocked by 4 issues on Jul 29, 2026

   • 0.1.8 Beta2: Implement runtime-derived tool compatibility for custom Responses endpoints #58
   • 0.1.8 Beta1: Replace the internal Kimi K2.6 seed with K2.7 Code #250
   • 0.1.8 Beta2: Isolate V1 repair from V2 namespace adaptation #198
   • Preserve Codex agents configuration across Gateway overlay lifecycle #199
4. NOirBRight

   marked this as blocking on Jul 29, 2026

   • 0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257
5. NOirBRight

   added a parent issue on Jul 29, 2026

   • Spec: CodexHub 0.1.8 staged compatibility and release roadmap #248
6. NOirBRight

   removed a parent issue on Jul 29, 2026

   • Spec: CodexHub 0.1.8 staged compatibility and release roadmap #248
7. NOirBRight

   added a parent issue on Jul 29, 2026

   • 0.1.8 Beta1 gate: Publish the stop-the-bleeding prerelease #258
8. NOirBRight

   unmarked this as blocking on Jul 29, 2026

   • 0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257
9. 8 remaining items

   Load more
10. NOirBRight

    marked this as blocked by 2 issues on Jul 31, 2026

    • 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282
    • 0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283
11. NOirBRight

    unmarked this as blocking on Jul 31, 2026

    • 0.1.8 Beta1 gate: Publish the stop-the-bleeding prerelease #258
12. NOirBRight

    marked this as blocking on Jul 31, 2026

    • 0.1.8 Beta4 gate: Publish the runtime-derived generic Collaboration V2 candidate #284
13. NOirBRight

    changed the title [-]0.1.8 Beta3: Qualify model-visible Collaboration V2[/-] [+]0.1.8 Beta4: Qualify model-visible Collaboration V2[/+] on Aug 1, 2026
14. NOirBRight

    changed the title [-]0.1.8 Beta4: Qualify model-visible Collaboration V2[/-] [+]0.1.8 Beta5: Validate Collaboration V2 through the generic compatibility layer[/+] on Aug 4, 2026
15. NOirBRight

    unmarked this as blocked by 3 issues on Aug 4, 2026

    • 0.1.8 Beta2: Implement runtime-derived tool compatibility for custom Responses endpoints #58
    • 0.1.8 Beta2: Isolate V1 repair from V2 namespace adaptation #198
    • 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64
16. NOirBRight

    changed the title [-]0.1.8 Beta5: Validate Collaboration V2 through the generic compatibility layer[/-] [+]0.1.8 Beta4: Complete the generic Collaboration V2 workflow[/+] on Aug 4, 2026
17. NOirBRight

    unmarked this as blocked on Aug 4, 2026

    • 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282
18. NOirBRight

    added

    campaign:0.1.8-beta40.1.8 Beta4 generic Collaboration V2 campaign0.1.8 Beta4 generic Collaboration V2 campaign

    on Aug 4, 2026
19. NOirBRight

    added a sub-issue on Aug 10, 2026

    • 0.1.8 Beta4: Reconcile the exact Codex Collaboration V2 runtime/wire contract #392
20. NOirBRight commented on Aug 10, 2026

    

    NOirBRight

    on Aug 10, 2026

    OwnerAuthor

    More actions

    Complete on the Beta4 candidate lineage. All four required inputs are closed: #392 (runtime/wire contract), #199 (user-owned agent configuration), #282 (native/adapt lifecycle implementation, PR #406), #283 (complete lifecycle verification, PRs #415/#416).

    Criteria mapping:

    • V1/V2 selection before schema injection, repair, state, or scheduler: verified by 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282 implementation and 0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283 static invariants (V2 branches set include_spawn_agent=False, subagent_state=None; V1 guidance/repair structurally skipped).
    • Exact runtime V2 direct tools, calls, results, status, task identity, message/agent_message, parent delivery, streaming, history remain native or reversibly adapted: verified end-to-end by the real CLI 0.146.1 full lifecycle (docs/evidence/issue-283/cli-native) and protocol fixture native/adapted/streaming cases (docs/evidence/issue-283/protocol-fixture). The one adaptation added during verification (empty-string void results normalized to null) is reversible and regression-tested.
    • Essential non-representable lifecycle fails before upstream sampling: verified by 0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283 fixture C4 negative cases (fail-before-mutation classifications).
    • User-owned agent configuration survives supported overlay/restart transitions: verified by Preserve Codex agents configuration across Gateway overlay lifecycle #199 and the 0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283 same-Home restart smoke (config hash unchanged, task files intact).
    • Codex Client remains the agent owner/executor; no V2-to-V1 downgrade, model fallback, model-name branch, runtime allowlist, history rewrite, or cross-Provider execution: verified by fixture assertions (cross_provider_requests=0, fallback_count=0) and static review.

    Deferred per this issue's scope: maintained GLM-5.2 / K2.7 Code / DeepSeek V4 Flash 0731 Provider regressions move to Beta5.
21. NOirBRight

    closed this as completedon Aug 10, 2026