chore: v1.0 beta->stable promotion pass (toolbox tools + orchestration/patterns/policy)#130
Merged
Merged
Conversation
…/patterns/policy) First freeze-prep promotion pass (markers only — additive, nothing removed/renamed). Promoted to @stable: - 24 mature toolbox tools (calculator/code/db/email/github/linear/notion/pdf/search/slack), 4-15 releases old with frozen signatures - SessionSearchResult, agent.PlanningConfig Module promises upgraded to stable (surfaces already fully @stable since v0.25): - orchestration (+checkpoint/graph/node/state/supervisor), patterns (+debate/plan_and_execute/reflective/team_lead), policy - EXPECTED_MODULE_STABILITY updated to match (architecture test is the gate) Held @beta deliberately: - v0.27.0 additions (recall tool, injection guardrail, cache-cost, Mongo/Dynamo) — one more cycle - evals stays a beta MODULE: surface is 71-beta/7-stable (50 evaluator classes still growing); the 7 core types stay @stable Added scripts/stability_audit.py (reproducible mismatch report). Architecture gate 1192 passed; mypy clean; full suite 7638 passed / 0 failed.
5 tasks
johnnichev
added a commit
that referenced
this pull request
Jun 15, 2026
Ships the beta->stable promotion pass (24 toolbox tools, orchestration/patterns/policy module promises, SessionSearchResult, PlanningConfig) merged in #130. Version 0.28.0->0.29.0, CHANGELOG [0.29.0] synced, README What's New v0.29, version stamps, llms-full regenerated via scripts/build_llms_full.py.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First v1.0 API-freeze promotion pass. Markers only — additive, nothing removed or renamed. Driven by the review note (cross-referencing each symbol's marker against its module's ROADMAP promise).
Promoted to @stable
SessionSearchResult,agent.PlanningConfig.Module promises upgraded to stable
orchestration(+ checkpoint/graph/node/state/supervisor),patterns(+ debate/plan_and_execute/reflective/team_lead),policy. Their public surfaces were already 100%@stable(the v0.25 promotion sweep); this aligns the module-level promise.EXPECTED_MODULE_STABILITYupdated so the architecture test stays the gate.Held @beta deliberately
make_recall_tool,PromptInjectionGuardrail,calculate_cost_with_cached_input,MongoSessionStore,DynamoDBSessionStore) — one more cycle.evalsstays a beta module — a data-driven deviation from the original "upgrade all four" plan: its surface is 71-beta / 7-stable (the 50 evaluator classes are still growing), so promising the module stable would be a false promise. Its 7 core types (EvalSuite/TestCase/EvalReport/…) remain@stable.Tooling
scripts/stability_audit.py— reproducible report of symbols whose marker disagrees with their module promise. After this pass: promotion candidates 42→17, lagging modules 94→13 (the remainders are the intentional holds).Verification
Lands in
[Unreleased]; ships with the next release (1.0 freeze or 0.29.0).