Repository navigation
0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate #281
Description
Parent
Release purpose
Publish 0.1.8-beta.3 after the generic client-executed tool_search and reversible Code Mode workflows are complete.
This phase extends the generic Beta2 compatibility layer. It does not perform the formal GLM/K2.7 maintained-Provider regression.
Required inputs
- Previous cumulative release gate: 0.1.8 Beta2 gate: Publish the custom-endpoint tool compatibility foundation #318.
- Generic client tool discovery: 0.1.8 Beta3: Complete the generic client tool_search lifecycle #63, 0.1.8 Beta3: Implement the generic client tool_search protocol adapter #277, and 0.1.8 Beta3: Verify the complete generic client tool_search workflow #278.
- Generic reversible Code Mode: 0.1.8 Beta3: Complete the generic reversible Code Mode workflow #251, 0.1.8 Beta3: Implement the generic reversible custom/freeform Code Mode codec #279, and 0.1.8 Beta3: Verify the complete generic Code Mode workflow #280.
- Official Collaboration capability matrix: 0.1.8 Beta3: Qualify official Collaboration V1/V2 support for the catalog #369.
- Per-model V1/V2 override UI/materializer: 0.1.8 Beta3: Persist and expose per-model Collaboration V1/V2 overrides (Luna V2) #368.
- Ollama Responses timeout/stream classification: 0.1.8 Beta3: Diagnose Ollama Responses timeouts and classify stream failures #370.
Acceptance criteria
- The exact beta.2 candidate lineage is preserved.
- 0.1.8 Beta3: Complete the generic client tool_search lifecycle #63 and 0.1.8 Beta3: Complete the generic reversible Code Mode workflow #251 are closed with protocol-controlled real-CLI evidence.
- Native-compatible shapes remain native and only incompatible reversible shapes use Adapters.
- No Provider/model name selects production behavior or test eligibility.
- Hosted search is not confused with client tool discovery and is never proxied through another Provider.
- Exact route identity and all Beta1/Beta2 regressions remain green.
- 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.3tagged and published as a manual opt-in prerelease.
Out of scope
- Third-party Collaboration V2 full lifecycle, maintained-Provider full regression, Chat, and cross-Provider proxying.
Blocked by
- 0.1.8 Beta2 gate: Publish the custom-endpoint tool compatibility foundation #318
- 0.1.8 Beta3: Complete the generic client tool_search lifecycle #63
- 0.1.8 Beta3: Complete the generic reversible Code Mode workflow #251
- 0.1.8 Beta3: Persist and expose per-model Collaboration V1/V2 overrides (Luna V2) #368
- 0.1.8 Beta3: Qualify official Collaboration V1/V2 support for the catalog #369
- 0.1.8 Beta3: Diagnose Ollama Responses timeouts and classify stream failures #370
Activity
[-]0.1.8 Phase 2 gate: Publish the beta.2 advanced-tools candidate[/-][+]0.1.8 Phase 3 gate: Publish the beta.3 advanced-tools candidate[/+][-]0.1.8 Phase 3 gate: Publish the beta.3 advanced-tools candidate[/-][+]0.1.8 Beta4 gate: Publish the advanced client-workflow candidate[/+][-]0.1.8 Beta4 gate: Publish the advanced client-workflow candidate[/-][+]0.1.8 Beta3 gate: Publish the generic advanced-tool workflow candidate[/+]NOirBRight commentedon Aug 7, 2026
Beta3 gate addition: #370 reasoning regression
The cumulative Beta3 gate now explicitly consumes #370. Before this issue can close, the candidate must include:
The release order remains implementation -> exact candidate-SHA review -> CLI/manual verification -> local verification gate -> tag/prerelease. #252/#282/#283/#284 remain Beta4 dependencies.
Plan:
docs/superpowers/plans/2026-08-07-beta3-advanced-responses-and-reasoning.mdReferences: