Repository navigation
0.1.8 Beta2: Isolate V1 repair from V2 namespace adaptation #198
Description
Parent
Outcome
Make Collaboration V1 repair structurally unable to run on a V2 request before the generic Beta2 compatibility layer is enabled.
Required behavior
- Resolve the V1/V2 boundary from 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64 before tool-schema injection, semantic repair, state handling, or scheduler logic.
- Keep the proven V1 compatibility path unchanged for an actual V1 request.
- For V2, bypass all V1-only injection, repair, state, scheduler, close/resume, and result parsing.
- Let 0.1.8 Beta2: Implement runtime-derived tool compatibility for custom Responses endpoints #58 classify the V2 namespace as
native, reversibleadapt,omit, orrequired-but-unavailablefor the already-selected protocol. - Never silently downgrade V2 to V1 and never choose another model or Provider.
- CodexHub may adapt a namespace encoding but never creates agents, invents task paths, executes tools, or fabricates completion.
Acceptance criteria
- Table-driven tests cover explicit V1, explicit V2, metadata/feature selection, unknown state, and conflicting inputs.
- No V2 request receives V1
fork_context, agent-ID targets, close/resume, scheduler, state machine, or wait-result repair. - A representable V2 namespace reaches the generic compatibility planner without model-name dispatch.
- An unavailable required V2 tool fails before upstream sampling with a stable sanitized classification.
- Official transparent routing and existing V1 behavior remain unchanged.
- Telemetry contains no prompts, tool arguments/results, credentials, call IDs, or task paths.
Non-goals
- Full Collaboration V2 workflow qualification or advertisement.
- Gateway-owned agent execution.
- Cross-Provider proxying.
- Changing the official/default V1/V2 metadata.
Activity
NOirBRight commentedon Jul 29, 2026
0.1.8 Beta1 role
This is a mandatory corruption-prevention prerequisite for #252, not evidence that V2 is enabled. A route must select one collaboration backend before model-visible tools or repair logic are constructed; unknown/conflicting metadata fails closed, and V1-only repair/scheduler behavior cannot run on V2.
11 remaining items
NOirBRight commentedon Aug 4, 2026
Orchestrator dispatch status (2026-08-04)
Campaign:
campaign:0.1.8-beta2.Dispatch is held by
#64and#350. One Luna Max worker will own the V1 repair/V2 namespace isolation implementation and regression tests only after the schema boundary is accepted. No cross-Provider proxy, model fallback, or gateway-owned Collaboration scheduling is permitted.NOirBRight commentedon Aug 5, 2026
Beta2 dispatch update after #64
#64 and #350 are now complete on the current dev lineage. This issue is therefore unblocked for its narrow Beta2 corruption-prevention scope.
The worker must implement only:
Do not implement full Collaboration V2 lifecycle, tool compatibility classification from #65, model/provider fallback, cross-Provider proxying, Gateway-owned agent execution, or any release/tag action. The old Beta4 placement note is superseded for this narrow foundation; full V2 qualification remains Beta4.
NOirBRight commentedon Aug 5, 2026
Beta2 implementation update (2026-08-05)
#198 is implemented on exact candidate SHA
5c07d69320ee120b46ee1b594440fa0b3078cb37in draft PR #360.invalid_collaboration_boundary; diagnostics contain only classification.Local verification: focused 34 passed; routing 599 passed + 223 subtests; chat gateway 101 passed + 10 subtests; partition completeness, compile, and diff checks passed. Full Python core: 1898 passed, 1 skipped, with 3 failures reproduced unchanged on
origin/devbaseline (CI-doc fallback assertion and two Issue108 replay fixtures).Standards/Spec exact-SHA review passed; one non-blocking maintainability note remains that the runtime contract mirrors the evidence-only #64 inventory. No Beta2 tag or release action was taken.
NOirBRight commentedon Aug 5, 2026
Merged via PR #360 at exact reviewed head 5c07d69; squash commit dcd2f79 is now on dev. Focused and affected local suites were accepted before merge; no release/tag action was taken.