Skip to content

0.1.8 Beta3: Implement the generic client tool_search protocol adapter #277

Closed

Description

@NOirBRight

Parent

#63 (part of #248)

Outcome

Implement the generic protocol adapter for Codex client-executed tool_search.

The implementation is derived from the runtime declaration and selected upstream protocol. It must not depend on Provider or model names.

Required behavior

  • Preserve tool_search natively when the selected protocol can carry the Codex shape.
  • Otherwise encode it through one reversible request-scoped representation.
  • Inverse-map search call, search output, discovered declarations, subsequent call/result, streaming events, and replay history.
  • Preserve IDs, ordering, and declaration identity.
  • Keep hosted search separate: it is available only when the already-selected Provider supports it and is never used as a substitute.

Acceptance criteria

  • Deterministic protocol fixtures cover native and adapted declaration/call/output/history forms.
  • Added/delta/done event ordering is assembled before final validation.
  • Unknown aliases, collisions, malformed output, missing/duplicate IDs, and ambiguous inverse mapping fail safely.
  • No model-name or maintained-Provider branch selects the Adapter.
  • No request reaches a second Provider.
  • Diagnostics contain no prompt, tool arguments/results, credentials, call IDs, or user content.

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 GLM-5.2 explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta3: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/+] on Aug 1, 2026
  3. changed the title [-]0.1.8 Beta3: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta4: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/+] on Aug 4, 2026
  4. changed the title [-]0.1.8 Beta4: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/-] [+]0.1.8 Beta3: Implement the generic client tool_search protocol adapter[/+] 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 generic client-owned tool_search implementation and native/adapted lifecycle evidence are recorded in docs/evidence/issue-63/ and docs/evidence/issue-278/. Fresh preflight validation passed with scripts/validate_issue_63_evidence.py --require-final-candidate, the bound #278 summary validator, and tests/test_beta3_protocol_cli_runner.py (12 passed). #63 and the Beta3 gate #281 are closed. Closing this stale child issue as delivered; no Beta4 code work is being added.

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