Repository navigation
0.1.8 Beta7 gate: Publish the stability and release-evidence candidate #319
Description
Parent
Release purpose
Publish 0.1.8-beta.7, the final planned beta and frozen input to RC. This phase adds no capability; it closes stability, persistence, availability, retry, and bounded release-evidence work.
Required inputs
- Previous cumulative release gate: 0.1.8 Beta6 gate: Publish usable Ollama Chat with complete Collaboration V2 #259.
- Provider navigation and persisted-route safety: Clarify Provider navigation state after Save or endpoint errors #83 and Keep legacy persisted provider aliases on the selected route across connect/disconnect #203.
- Maintained-Provider support/availability diagnostics: 0.1.8 Beta7: Separate maintained-Provider regression status from transient availability #247.
- Bounded real-client capture: Harden bounded real-client capture and preserve the accepted 0.1.7 profile #244.
- Versioned CLI-only release-verification profile: 0.1.8 Beta7: Add the versioned CLI-only release-verification profile #255.
- Bounded request-local retry policy: 0.1.8 Beta7: Bound request-local retries without circuit breaking #256.
- Draft PR fix(issue62): integrate bounded live-control evidence hardening #349 disposition: 0.1.8 Beta7: Re-scope reusable evidence hardening from draft PR #349 #352 must be reviewed and either narrowed to required Beta7/RC work or closed without merge. It must not re-expand 0.1.8 Beta2: Inventory Codex CLI 0.146 tool types and representative Responses lifecycles #62.
Closed #268 remains the process-tree teardown invariant.
Acceptance criteria
- 0.1.8 Beta6 gate: Publish usable Ollama Chat with complete Collaboration V2 #259, Clarify Provider navigation state after Save or endpoint errors #83, Keep legacy persisted provider aliases on the selected route across connect/disconnect #203, 0.1.8 Beta7: Separate maintained-Provider regression status from transient availability #247, Harden bounded real-client capture and preserve the accepted 0.1.7 profile #244, 0.1.8 Beta7: Add the versioned CLI-only release-verification profile #255, 0.1.8 Beta7: Bound request-local retries without circuit breaking #256, and 0.1.8 Beta7: Re-scope reusable evidence hardening from draft PR #349 #352 are closed on one cumulative lineage or with an explicit no-change disposition where allowed.
- The accepted 0.1.7 profile remains immutable and replayable.
- The 0.1.8 profile covers every shipped phase plus Beta1 regressions without raw content or unbounded work roots.
- Provider save/refresh failures, legacy aliases, transient availability, retries, teardown, and cleanup have deterministic typed outcomes.
- No hidden POST retry, selective evidence replacement, model fallback, or cross-Provider tool execution can turn a degraded/failed attempt into a pass.
- Exact candidate SHA review is accepted, then CLI/manual verification is accepted, then local verification gate succeeds.
- Only after those gates pass is
0.1.8-beta.7tagged and published as a manual opt-in prerelease. - After publication the lineage is frozen for RC; any product-code change requires a new beta or RC candidate with affected evidence rerun.
Out of scope
- New capabilities, Providers, protocols, or client integrations.
- Executing the four fixed RC 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).
- Stable promotion.
Activity
NOirBRight commentedon Aug 1, 2026
Agent Brief
Category: enhancement
Summary: Publish the final 0.1.8 beta after stability fixes and the complete bounded CLI qualification profile are ready.
Current behavior:
The roadmap has a usable Chat gate and an RC aggregate, but no public candidate between substantial stability/profile changes and the fixed RC qualification runs.
Desired behavior:
One cumulative 0.1.8-beta.6 candidate closes all known release-hardening tickets, proves bounded deterministic evidence handling, and becomes the frozen input to RC qualification.
Key interfaces:
Acceptance criteria:
Out of scope:
5 remaining items
[-]0.1.8 Beta6 gate: Publish the stability and qualification candidate[/-][+]0.1.8 Beta7 gate: Publish the stability and release-evidence candidate[/+]