Skip to content

0.1.8 Beta3: Verify the complete generic Code Mode workflow #280

Closed

Description

@NOirBRight

Parent

#251 (part of #248)

Outcome

Verify the complete generic Code Mode workflow through the real Codex CLI and a protocol-controlled upstream fixture.

This verifies CodexHub's codec and lifecycle independently from a named Provider/model regression.

Acceptance criteria

  • One native-compatible case and one adapted case complete declaration, call, Codex-owned execution, output, follow-up, streaming, interruption where applicable, and replay.
  • The real read -> target-scoped apply_patch -> verify workflow completes without Gateway-owned execution.
  • Both paths preserve exact IDs, order, and selected route identity.
  • Collision, malformed input, unknown alias, and missing/duplicate ID controls fail safely.
  • No hidden model fallback or cross-Provider request occurs.
  • Evidence is bounded, sanitized, and candidate/CLI/protocol bound.

Blocked by

Activity

  1. added
    enhancementNew feature or request
    ready-for-agentFully specified, ready for an AFK agent
    wayfinder:taskWayfinder implementation task
    tier:heavyOrchestrator provider tier: heavy
    P1Priority 1: current iteration goal
    on Jul 31, 2026
  2. changed the title [-]0.1.8 Beta2: Extend the Code Mode round trip to K2.7 Code[/-] [+]0.1.8 Beta3: Extend the Code Mode round trip to K2.7 Code[/+] on Aug 1, 2026
  3. changed the title [-]0.1.8 Beta3: Extend the Code Mode round trip to K2.7 Code[/-] [+]0.1.8 Beta4: Extend the Code Mode round trip to K2.7 Code[/+] on Aug 4, 2026
  4. changed the title [-]0.1.8 Beta4: Extend the Code Mode round trip to K2.7 Code[/-] [+]0.1.8 Beta3: Verify the complete generic Code Mode workflow[/+] on Aug 4, 2026
  5. NOirBRight commented on Aug 10, 2026

    @NOirBRight
    OwnerAuthor

    Completion receipt (Beta4 preflight audit, 2026-08-10): the accepted Beta3 implementation candidate is 7006542a773fc20c10e4bbcadd593393a259ceb2; it was promoted in v0.1.8-beta.3 and remains in the cumulative v0.1.8-beta.3.3 lineage (d1308ce5bd0546993a68579b23102bafde24513a). GitHub Actions remains disabled; local evidence is authoritative.
    The native/adapted shell_command -> apply_patch -> shell_command CLI workflows and exact lifecycle provenance are recorded in docs/evidence/issue-278/summary.json, bound to the accepted Beta3 candidate. Fresh summary validation and tests/test_beta3_protocol_cli_runner.py passed (12 passed). #251 and #281 are closed. Closing this stale child issue as delivered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Priority 1: current iteration goalcampaign:0.1.8-beta30.1.8 Beta3 generic advanced-tool workflows campaignenhancementNew feature or requestready-for-agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation task

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions