Repository navigation
0.1.8 Beta2 gate: Publish the custom-endpoint tool compatibility foundation #318
Description
Parent
Release purpose
Publish 0.1.8-beta.2 as the generic custom-endpoint tool compatibility foundation. Beta2 does not qualify named models and does not make GLM/K2.7 a runtime allowlist.
Completed prerequisites retained
- Serialize DiagnosticControlBridge batches to prevent duplicate control execution #267 and Pass current-session identity through the Rust port-restart lifecycle test fixture #269 — deterministic test/lifecycle regressions.
- 0.1.8 Beta2 prerequisite: Honor Codex visibility and keep internal reviewer models out of managed catalogs #273 and 0.1.8 Beta2 prerequisite: Fail closed on model identity mismatches instead of alias or catalog fallback #274 — official visibility and exact no-fallback model identity.
- 0.1.8 Beta2: Preserve explicit model-catalog overrides across sync and restart #327 — user-owned catalog overrides and paths.
- Beta1 usability regressions, including Official continuation and provider-scoped context windows.
Required open inputs
- Architecture and decision: 0.1.8 Beta2: Record the runtime-derived tool compatibility architecture (ADR-0002) #350 and 0.1.8 Beta2: Approve the custom-endpoint tool compatibility contract #249.
- Exact CLI structural inventory and compatibility rules: 0.1.8 Beta2: Inventory Codex CLI 0.146 tool types and representative Responses lifecycles #62, 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64, and 0.1.8 Beta2: Define tool-type compatibility rules for custom Responses endpoints #65.
- V1/V2 corruption guard: 0.1.8 Beta2: Isolate V1 repair from V2 namespace adaptation #198.
- Runtime-derived compatibility implementation: 0.1.8 Beta2: Implement runtime-derived tool compatibility for custom Responses endpoints #58.
Acceptance criteria
- Every required input above is closed on the candidate lineage.
- The user-selected Provider/model remains exact and immutable; no missing or incompatible tool causes model fallback.
- Runtime declarations resolve deterministically to
native,adapt,omit, orrequired-but-unavailable. - Native-compatible tools remain native; only incompatible reversible shapes use Adapters.
- Unsupported hosted search, compaction, and other hosted tools are not exposed.
- Network evidence proves there is no explicit or implicit cross-Provider tool proxy.
- The Gateway does not execute tools or schedule agents.
- Unknown custom endpoints use the same generic conservative path without a model-specific eligibility gate.
- No GLM/K2.7/model-name production codec branch is introduced.
- Beta1 visibility, identity, catalog ownership, continuation, and context-window regressions remain green.
- No alternate-codec retry or model-output format repair is added in Beta2.
Required publication order
- Implementation complete.
- Exact candidate SHA review accepted.
- CLI/manual verification accepted.
- local verification gate succeeds on that exact lineage.
- Only then tag and publish
0.1.8-beta.2as a manual opt-in prerelease.
Any incomplete or failed gate stops publication.
Out of scope
- Full maintained-Provider regression; 0.1.8 Beta5: Run the full maintained GLM-5.2 Provider regression #275/0.1.8 Beta5: Run the full maintained K2.7 Code Provider regression #276 and 0.1.8 Beta5 gate: Publish the three-route maintained-Provider Responses candidate #351 own Beta5.
- Advertising support for a named third-party model.
- Full Code Mode, tool discovery, or Collaboration V2 workflow qualification.
- Chat compatibility.
- Cross-Provider hosted-tool proxying.
- The expanded forensic evidence platform from draft PR fix(issue62): integrate bounded live-control evidence hardening #349; 0.1.8 Beta7: Re-scope reusable evidence hardening from draft PR #349 #352 owns any retained later work.
Activity
NOirBRight commentedon Aug 1, 2026
Agent Brief
Category: enhancement
Summary: Publish the cumulative 0.1.8-beta.2 core Responses candidate after every route, catalog, identity, evidence, and diagnostic prerequisite is accepted.
Current behavior:
0.1.8-beta.1 is published as the usability hotfix candidate. The deferred core Responses work is spread across evidence, decision, routing, model tracer, visibility, identity, and diagnostic tickets, but previously had no dedicated publication gate.
Desired behavior:
One exact cumulative candidate publishes only the independently qualified core Responses contract for GLM-5.2 and K2.7 Code. Every unqualified or internal semantic fails closed and later-phase tools remain unadvertised.
Key interfaces:
Acceptance criteria:
Out of scope:
NOirBRight commentedon Aug 2, 2026
Agent-brief correction: the immediate deterministic regression lane contains both #267 and #269. #269 is only partially covered by merged PR #297; its narrowed exact-identity controls and repetition contract remain open and block this gate.
34 remaining items
NOirBRight commentedon Aug 4, 2026
Beta2 campaign orchestration update — 2026-08-04
CI / gate; merge commit:7c792a057961d7e1fd6de61919be6eafb4e1967f.devcandidate; it remains evidence-only and does not unlock 0.1.8 Beta2: Define tool-type compatibility rules for custom Responses endpoints #65 until its full acceptance contract is true.NOirBRight commentedon Aug 4, 2026
#62 review blocker — do not merge current head
Exact-SHA review of PR #355 found that its current metadata relabels a 2026-07-12 capture (historically CLI 0.144) as CLI 0.146, although CLI 0.146 was released later. This is a provenance failure, not a harmless version update. The worker is correcting it by preserving historical metadata and marking any 0.146 source-contract evidence as unobserved/unqualified unless a genuinely post-release isolated capture exists. #62 remains open; #65 and all downstream Beta2 gates stay locked.
NOirBRight commentedon Aug 4, 2026
Orchestrator release gate (2026-08-04)
Campaign:
campaign:0.1.8-beta2.This gate is not a worker implementation shortcut. It opens only after #62, #64, #65, #198, #249, and #58 are closed on one candidate lineage. The final order is implementation complete → exact-SHA review → CLI/manual verification → Hosted
CI / gate→ tag/release. Any missing gate stops publication; no Beta2 tag/release exists yet.NOirBRight commentedon Aug 4, 2026
CI blocker update (2026-08-04)
Hosted run 30904259353 on the #62 candidate exposed two unrelated Rust debug lifecycle fixture failures. They are tracked in new P1 #356 and are being handled by a separate Luna Max worker with test-only scope. #356 must produce a new exact candidate with focused 10x normal/debug repetitions and a full Hosted matrix; no retry of the failed job is accepted. This does not change #62's evidence contract or unlock #65.
NOirBRight commentedon Aug 4, 2026
Decision: local verification only (2026-08-04)
Per maintainer direction, GitHub Actions CI is disabled for CodexHub (
CIworkflow state:disabled_manually). TheCI / gaterequired status check was removed from bothdevandmain; branch protection itself remains in place.From this point through Beta2, Beta3, Beta4, Beta5, Beta6, Beta7, RC1, and stable:
Existing Hosted run links are historical evidence only. No ticket may wait for or claim a Hosted
CI / gateresult.NOirBRight commentedon Aug 5, 2026
Beta2 orchestration update (2026-08-05)
#198 implementation is complete on draft PR #360 at exact SHA
5c07d69320ee120b46ee1b594440fa0b3078cb37, with local focused/affected verification recorded on #198.The next runtime implementation #58 remains blocked by the product decision/compatibility-table inputs #249 and #65. Per the current decision, #65 is intentionally deferred; no #58 or Beta2 release/tag action is starting until that decision changes. GitHub Actions remains disabled and no Hosted result is being claimed.
NOirBRight commentedon Aug 5, 2026
Beta2 gate reconciliation after #58 merge (2026-08-06)
The Beta2 dependency chain is now complete on
devfor the generic tool-compatibility core:4962400c369502ac49b504e142656bc9a61e0571; the exact implementation candidate521be91524d1a40fffc5464e3e7c7c04d312d357passed Standards/Spec review, local suites, and a real Codex CLI 0.145.0 → GLM-5.2 smoke.Next step is an internal
0.1.8-beta.2candidate from the exact currentdevSHA. Publication remains gated: exact candidate SHA review → CLI/manual verification → local release checklist → final tag/prerelease. No formal tag or release is created until every gate passes.NOirBRight commentedon Aug 6, 2026
Beta2 publication completed.
main:48efb0a91dfe5533dff5ee0b0f13e4acd913cb8c.b70414f575448748bdf26aff15594d8e8c8ed959.Published prerelease: https://github.com/NOirBRight/CodexHub/releases/tag/v0.1.8-beta.2
The tag is annotated and resolves to the final commit. Beta2 remains a generic custom-endpoint/tool-compatibility foundation; it does not advertise named third-party model qualification or cross-Provider hosted-tool proxying.
NOirBRight commentedon Aug 7, 2026
Beta2 hotfix follow-up publication completed.
v0.1.8-beta.2.1is a prerelease hotfix on top of the completed Beta2 generic tool-compatibility foundation.main:62edc398ef8c25a1474bbea712c481a80e8b53c0.