0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle #283

Activity

1. NOirBRight

   added this to the 0.1.8 — Responses, Chat & CLI stability milestone on Jul 31, 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 31, 2026
3. NOirBRight

   added a parent issue on Jul 31, 2026

   • 0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252
4. NOirBRight

   marked this as blocking on Jul 31, 2026

   • 0.1.8 Beta4: Complete the generic Collaboration V2 workflow #252
5. NOirBRight

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

   • 0.1.8 Beta5: Run the full maintained K2.7 Code Provider regression #276
   • 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282
6. NOirBRight

   changed the title [-]0.1.8 Beta3: Extend Collaboration V2 to K2.7 Code[/-] [+]0.1.8 Beta4: Extend Collaboration V2 to K2.7 Code[/+] on Aug 1, 2026
7. NOirBRight

   changed the title [-]0.1.8 Beta4: Extend Collaboration V2 to K2.7 Code[/-] [+]0.1.8 Beta5: Complete the K2.7 Code Collaboration V2 lifecycle regression[/+] on Aug 4, 2026
8. NOirBRight

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

   • 0.1.8 Beta5: Run the full maintained K2.7 Code Provider regression #276
   • 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282
9. NOirBRight

   marked this as blocked by 2 issues on Aug 4, 2026

   • Preserve Codex agents configuration across Gateway overlay lifecycle #199
   • 0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281
10. NOirBRight

    changed the title [-]0.1.8 Beta5: Complete the K2.7 Code Collaboration V2 lifecycle regression[/-] [+]0.1.8 Beta4: Verify the complete generic Collaboration V2 lifecycle[/+] on Aug 4, 2026
11. NOirBRight

    unmarked this as blocked on Aug 4, 2026

    • 0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281
12. NOirBRight

    marked this as blocked on Aug 4, 2026

    • 0.1.8 Beta4: Implement runtime-derived Collaboration V2 direct-tool and lifecycle adaptation #282
13. 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
14. NOirBRight

    added a commit that references this issue on Aug 10, 2026

    test(evidence): issue 283 real-client V2 lifecycle verification and v…

    ...

    b73ff43
15. NOirBRight commented on Aug 10, 2026

    

    NOirBRight

    on Aug 10, 2026

    OwnerAuthor

    More actions

    Verified and closed on the Beta4 candidate lineage. Evidence: PR #415 (protocol fixture, merged as 9e87a8e) and PR #416 (real-client lifecycle + request-shape smoke + void-result contract fix, merged as b73ff43); sanitized artifacts under docs/evidence/issue-283/.

    Acceptance criteria mapping:

    • Real CLI full lifecycle: PASS — real Codex CLI 0.146.1 exercised spawn_agent, send_message, followup_task, wait_agent, interrupt_agent, list_agents, child result delivery, parent completion (cli-native/summary.json, qualification_status: passed, turn.completed, no errors).
    • Native + adapted Responses variants: PASS — protocol fixture C1/C2 (18 cases) prove identical canonical lifecycle with reversible aliasing.
    • Codex App request-shape/same-Home smoke: PASS — app-server stdio capture shows collaboration namespace + six direct tools, no multi_agent_v1, no fork_context, model unrewritten.
    • Same-Home restart/readback: PASS — config.toml SHA256 unchanged, task identity consistent, no task files deleted/rewritten.
    • Negative cases fail before mutation: PASS — fixture C4 (mixed V1/V2, missing/duplicate IDs, malformed agent_message, cross-Home, incompatible paginated state) all fail closed with expected classifications.
    • V1 repair/scheduler absent from V2: PASS — static invariants (include_spawn_agent=False, subagent_state=None in V2 branches) + event-log assertions.
    • Gateway never owns/schedules/forges: PASS — fixture asserts no fabricated function_call_output/completion, cross_provider_requests=0, fallback_count=0.
    • No model fallback / cross-Provider execution: PASS.
    • Existing task files untouched: PASS.
    • Evidence bounded/sanitized/candidate-bound (candidate_sha 5bb5ce5 lineage): PASS.

    Note: one additional contract bug was found and fixed during verification — the real CLI serializes void-result tools (send_message/followup_task) as empty string, while the contract demanded JSON null; empty string is now reversibly normalized to null at the boundary (src-python/collaboration_runtime_contract.py:433, regression tests in tests/test_issue_282_collaboration_v2.py).
16. NOirBRight

    closed this as completedon Aug 10, 2026