Prepare 2.3.0 with GPT-6.1 Sol preferred routing

docs/behavior-scenarios.md

@@ -22,14 +22,14 @@ These are static review cases, not a record that a model executed them. Use them
 | User says never delegate | Stay local even if a skill is selected implicitly |
 | Authorized batch of known-source records with fixed checks | Consider GPT-6 Luna low/medium; batch useful work, no fan-out quota |
 | Authorized settled patch with contained failure and behavior checks | Consider GPT-6 Luna medium/high; parent reviews diff and checks |
-| Ordinary bug requires causal investigation across files | Select GPT-6 Sol medium directly; no mandatory Luna attempt |
+| Ordinary bug requires causal investigation across files | Select GPT-6.1 Sol medium directly when exposed; no mandatory Luna attempt |
 | Tiny diff changes a shared authorization contract | Parent owns the contract; size alone does not justify Luna |
 | Host exposes GPT-6 Sol and GPT-5.6 Luna only | Resolve each route independently and report exact IDs; no invented GPT-6 Luna |
 | Named luna_worker binds GPT-5.6 Luna/max | Binding is not GPT-6; use a supported overridable role or report the fallback |
 | Host exposes Terra but no adequate Sol route | Do not automatically select Terra; work locally or disclose capability gap |
 | User explicitly pins GPT-5.6 Terra | Preserve the pin; retirement from defaults does not authorize overriding the user |
 | User requires GPT-6 Luna but schema lacks it | Report unavailability before dependent dispatch; no silent older-generation substitute |
-| Luna is 20x cheaper at equal Standard token volumes | Do not infer equal task quality, twenty retries, more slots or Codex quota savings |
+| Luna input/output are 20x cheaper at equal Standard token volumes | Do not infer equal task quality, twenty retries, more slots or Codex quota savings; cached input has a different ratio |
 | Luna needs repeated parent correction | Reassess contract and choose Sol directly; count parent rework |
 | Missing actual usage, requested model known | Cost and observed identity remain unknown; no fabricated benchmark |
 | Several fixed independent reads, no delegation request | Use supported tool concurrency; no child just to wait on I/O |
@@ -53,6 +53,25 @@ These are static review cases, not a record that a model executed them. Use them
 | Several independent ready slices, parent only has later synthesis, host permits this dispatch | Run useful children concurrently and integrate on return; no universal requirement to invent simultaneous parent work |
 | Host explicitly requires useful concurrent parent work | Honor that stricter requirement even when the fleet policy otherwise permits parent waiting |
 
+## 2.3 Sol version and migration scenarios
+
+These are static expected decisions, not live executions or benchmarks.
+
+| Scenario | Expected behavior |
+| --- | --- |
+| Authorized investigation; schema exposes both gpt-6.1-sol and gpt-6-sol, no pin | Prefer gpt-6.1-sol medium; record the exact requested ID and keep observed identity unknown unless evidenced |
+| Host exposes GPT-6 Sol but not 6.1; no exact version requirement | Use an adequate explicit gpt-6-sol compatibility route; do not claim it ran 6.1 |
+| Parent picker has 6.1 but child schema lacks it | Check child support independently; use an adequate explicit compatibility route or local work |
+| User requires GPT-6.1 Sol, child schema lacks it | Report the exact gap before dependent dispatch; no silent old Sol substitute |
+| User pins gpt-6-sol or current parent is older Sol | Preserve the selection; installing the skill does not migrate active settings |
+| A fixed sol_worker binds gpt-6-sol | Keep its real identity; use a supported override only when authorized and compatible with fork rules |
+| Authorized API migration from old Sol with medium | Keep medium; do not raise effort solely because the version changed |
+| Authorized API migration uses none/minimal or Chat Completions tools | Start at supported low for effort and use Responses for tools; do not claim compatibility without those changes |
+| Desktop exposes Ultra for 6.1 | Follow actual host controls; do not send ultra as an API reasoning effort |
+| Mostly cached input and cost-sensitive routing | Use the cached-input category: Luna is 1/10 of 6.1 Sol, not 1/20; total task savings need actual usage |
+| New Sol is officially positioned near Astra | Use Sol for its work shape; retain useful Astra depth without mandatory participation or an unmeasured equivalence claim |
+| Archived synthetic packet requests gpt-6-sol | Validate it unchanged; never rewrite its requested identity as 6.1 |
+
 ## 2.0 escalation scenarios (manual forward evaluation)
 
 These expectations are not recorded live-agent outcomes.

docs/releases/2.3.0.md

@@ -0,0 +1,17 @@
+# 2.3.0 — GPT-6.1 Sol 首选路由
+
+## 变化
+
+- 新通用工程会话、常规开发、调查和复杂分析推荐 GPT-6.1 Sol / medium，按需 high。配置示例、技能入口、全局提示词和当前证据说明同步使用精确 ID `gpt-6.1-sol`。
+- 保留 GPT-6 Luna 的有界执行与 GPT-6 Astra 的最困难综合工作。6.1 的接近 Astra 表现来自官方定位，不能代替本项目对真实任务的质量、延迟与总成本评测。
+- 每条路线独立检查宿主支持。6.1 不可用时显式选择足够胜任的 GPT-6 Sol 或 GPT-5.6 Sol；旧模型不是别名，用户精确指定的版本、已有配置和活动主模型继续保留。
+- 补充 API 迁移边界：保留受支持的 effort；6.1 不支持 none/minimal，以 low 作为替代起点并验证。工具调用须使用 Responses，Desktop/CLI Ultra 等参数不能直接复制到 API。
+- 更新 2026-10-06 价格快照：6.1 输入/输出仍为 2/10 美元每百万 token，缓存输入由旧 Sol 的 0.20 降为 0.10。缓存比例与其他 token 类别分别计算，API 单价不代表 Codex 套餐消耗。
+
+## 兼容与验证边界
+
+证据 schema 1/2、决策 schema 1 和安装流程不变。历史发行说明与旧模型合成夹具保持原样，校验器继续接受旧版模型记录。静态行为场景覆盖混合宿主、精确版本要求、固定角色、effort 与计费差异；这些场景不声称执行过真实子智能体或性能基准。
+
+安装仍默认预览，不切换活动模型、不改 `config.toml`，不扩大委派权限或宿主容量。全局提示词安装仍须单独选择 `--include-prompt` 并审阅替换差异。版本号不表示远端标签或 Release 已创建。
+
+依据：[GPT-6.1 Sol](https://developers.openai.com/api/docs/models/gpt-6.1-sol)、[Codex 模型](https://learn.chatgpt.com/docs/models)、[迁移指南](https://developers.openai.com/api/docs/guides/latest-model?model=gpt-6.1-sol)、[API 价格](https://developers.openai.com/api/docs/pricing)。