Skip to content

0.1.8 Beta3: Verify the complete generic client tool_search workflow #278

Closed

Description

@NOirBRight

Parent

#63 (part of #248)

Outcome

Verify the complete generic client-executed tool_search workflow through the real Codex CLI and a protocol-controlled upstream fixture.

This verifies CodexHub's generic lifecycle independently from the behavior of any named Provider/model.

Acceptance criteria

  • Planner eligibility and the model-visible client tool_search declaration are captured before sampling.
  • An explicit-hint case completes search call/output, discovered declaration, subsequent call/result, streaming, and replay history.
  • A no-hint case distinguishes model non-selection from planner, upstream, runtime, and Gateway failure.
  • Native and adapted protocol variants exercise the same canonical lifecycle.
  • Hosted search cannot satisfy the case and no cross-Provider request occurs.
  • Exact user-selected route identity remains unchanged.
  • 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: Prove the K2.7 Code explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta3: Prove the K2.7 Code explicit-hint tool_search lifecycle[/+] on Aug 1, 2026
  3. changed the title [-]0.1.8 Beta3: Prove the K2.7 Code explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta4: Prove the K2.7 Code explicit-hint tool_search lifecycle[/+] on Aug 4, 2026
  4. changed the title [-]0.1.8 Beta4: Prove the K2.7 Code explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta3: Verify the complete generic client tool_search 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 four-case real Codex CLI 0.146.1 protocol-controlled summary is recorded in docs/evidence/issue-278/summary.json: native/adapted explicit cases complete the search/discovery/follow-up lifecycle and both no-hint cases classify model_not_selected. Fresh summary validation and the runner tests passed (12 passed). #63 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