Wayfinder: CodexHub 0.1.6–0.3.0 Gateway and release roadmap #147

This was generated by AI during triage.

Purpose

This is the release-level map. Detailed behavior and acceptance live in the linked specifications and leaf issues; native GitHub dependencies are authoritative for execution order.

Released

0.1.6 — Codex control-plane reliability

Released. The milestone and its closed issues retain the historical implementation/evidence record.

0.1.7 — Trustworthy stability chain

Released. The accepted real-client profile remains reproducible; 0.1.8 may harden its shared runner but must not silently redefine the 0.1.7 evidence contract.

Current: 0.1.8 — Responses, Chat & CLI stability

Parent specification: #248

0.1.8 keeps the approved capability roadmap but inserts the released usability Beta1 and shifts every later phase by one version.

1. 0.1.8-beta.1 — usability hotfix (released)
   • Gate 0.1.8 Beta1 gate: Publish the stop-the-bleeding prerelease #258; exact release SHA d9c5acb.
   • Urgent continuation/context fixes, Hosted CI migration, and release foundations.
2. 0.1.8-beta.2 — core Responses
   • Gate 0.1.8 Beta2 gate: Publish the custom-endpoint tool compatibility foundation #318.
   • Runtime/wire evidence, two-model decision, visibility/identity safety, GLM/K2.7 tracer bullets, and capability-driven routing.
3. 0.1.8-beta.3 — advanced client tools
   • Gate 0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281.
   • Reversible Code Mode and explicit-hint client-executed tool_search only.
4. 0.1.8-beta.4 — Collaboration V2
   • Gate 0.1.8 Beta4 gate: Publish the runtime-derived generic Collaboration V2 candidate #284.
   • Exact V1/V2 boundary, corruption prevention, configuration preservation, and both model lifecycles.
5. 0.1.8-beta.5 — usable Chat
   • Gate 0.1.8 Beta6 gate: Publish usable Ollama Chat with complete Collaboration V2 #259.
   • Runtime-field adaptation, progressive SSE, standard tools, and a real CLI read/patch/verify loop.
6. 0.1.8-beta.6 — stability and qualification freeze
   • Gate 0.1.8 Beta7 gate: Publish the stability and release-evidence candidate #319.
   • Provider/UI/persistence safety, bounded capture/teardown, typed availability, complete CLI profile, and bounded retries.
7. 0.1.8-rc.1 — fixed exact-candidate qualification
   • Gate 0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257 and route batches 0.1.8 RC1: Run the fixed GLM-5.2 Responses regression batch #287-0.1.8 RC1: Run the fixed K2.7 Chat regression batch #290.
8. Stable 0.1.8
   • Human promotion gate 0.1.8 stable gate: Promote the accepted RC lineage #320; any product-code change after RC requires requalification.

Every stage is cumulative, prerelease-only until #320, and bound to exact-SHA Hosted CI plus bounded real-Codex-CLI evidence. Beta1 regressions remain in every later profile.

Next: 0.1.9 — capability and protocol expansion

Planned after the 0.1.8 stability floor:

• Chat Code Mode/V2/custom/namespace/search parity where a reversible contract can be proven.
• Anthropic Messages and Claude Code integration (Implement and qualify Anthropic Messages as a Gateway upstream protocol #246).
• Curated Provider presets, onboarding, and discovery work (Bound Gateway client probes and catalog discovery work #28, Introduce curated Provider presets and managed authentication #71, Add a versioned Provider preset manifest and curated catalog #89, Add guided API-key Provider onboarding from curated presets #90, Add selective Models.dev sync and reviewed upstream diffs #91).
• Broad provider/model capability matrices and generalized native-route decisions (Spike complete Codex model capability exposure on third-party providers #57, Retire Gateway-owned Codex tool schemas and scheduling where the spike proves native behavior #59, Reconcile issue 57 evidence and record scoped route decisions #67).
• Complete cross-Home V2 topology/history migration (Preserve V2 agent topology and paginated history during consolidation #197).
• Evidence-driven retry-storm dampening/circuit breaking (Design retry-storm dampening with jitter, circuit breaker, and downstream notices #22), only if operational evidence justifies it.

Later

0.1.10 — Visible console completion

Keep the existing milestone for operator-facing console completion after the protocol foundation is dependable. Its leaf issues define its scope and do not block 0.1.8.

0.2.x–0.3.0

Reassess after 0.1.8/0.1.9 evidence. Do not pre-commit broad provider or client matrices before the capability contracts and qualification harness have demonstrated stable extension points.

Planning rules

• GitHub issue dependencies, milestones, labels, exact-SHA evidence, checks, and release assets are authoritative.
• A prerelease gate may unblock the next beta, but never automatically publishes main or stable.
• Unsupported provider-native hosted capabilities are reported explicitly, not emulated or counted as Gateway regressions.
• Release evidence never becomes green by hidden retry, selective case overwrite, or discarded failed batches.