Prepare 2.3.0 with GPT-6.1 Sol preferred routing

skills/codex-subagent-router/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: codex-subagent-router
-description: Route authorized Codex subagents across GPT-6 Luna, Sol and Astra; manage ownership, lifecycle and evidence. Use for delegation, routing decisions or subagent audits. Discovery alone does not authorize spawning.
+description: Route authorized Codex subagents across GPT-6 Luna, GPT-6.1 Sol and GPT-6 Astra; manage ownership, lifecycle and evidence. Use for delegation, routing decisions or subagent audits. Discovery alone does not authorize spawning.
 ---
 
 # Codex Subagent Router
 
-Version 2.2.0. For new general engineering sessions recommend GPT-6 Sol / medium, with high for demonstrated reasoning needs. Preserve the selected parent. Use Astra proactively for high-leverage difficult decisions, independent counterexample reviews and residual hard reasoning; neither prior failure nor a model quota is required.
+Version 2.3.0. For new general engineering sessions recommend GPT-6.1 Sol / medium, with high for demonstrated reasoning needs. Preserve the selected parent. Use Astra proactively for high-leverage difficult decisions, independent counterexample reviews and residual hard reasoning when its depth adds value over Sol; neither prior failure nor a model quota is required.
 
 Make delegation useful, observable and bounded. Preserve the selected parent model. The parent owns the critical path, shared decisions, integration and final acceptance. This skill neither changes configuration nor grants external permissions.
 
@@ -50,8 +50,8 @@ Stay local for a trivial task, no useful parallel benefit, an immediate dependen
 | --- | --- |
 | Known-source collection, fixed checks, logs | GPT-6 Luna low; medium for multi-step work |
 | Bounded classification, conversion, settled patch with fixed checks | GPT-6 Luna medium; high for local reasoning |
-| Everyday implementation, debugging, locating/correlating artifacts | GPT-6 Sol medium |
-| Bounded complex analysis, design or financial/security evidence | GPT-6 Sol medium/high |
+| Everyday implementation, debugging, locating/correlating artifacts | GPT-6.1 Sol medium |
+| Bounded complex analysis, design or financial/security evidence | GPT-6.1 Sol medium/high |
 | High-leverage difficult design, cross-system synthesis, independent high-impact counterexample review | GPT-6 Astra medium/high |
 | Shared decisions, integration and external/final gates | Current parent, serial |
 
@@ -59,11 +59,11 @@ Luna is the first candidate when inputs are bounded, the contract is settled, co
 
 These are starting heuristics, not measured task-cost rankings. Lower prices broaden the useful Luna workload; fill supported capacity with useful work under existing authorization, never infer extra host slots from price. Pick sufficient capability directly; do not escalate through every model. Missing access/data and tool failures need diagnosis, not a stronger model. After two same-class failures, stop that slice and return the evidence to the parent; escalate earlier when the contract no longer fits. Preserve useful evidence on handoff instead of restarting discovery.
 
-Resolve exact IDs from the child-tool schema: prefer `gpt-6-luna`, `gpt-6-sol`, `gpt-6-astra` only when exposed. GPT-5.6 models are explicit compatibility routes, not aliases for GPT-6. For a legacy-only host use [routing boundaries](references/routing-matrix.md); do not silently substitute an explicitly required generation. A role bound to GPT-5.6 Luna remains GPT-5.6 even when named `luna_worker`.
+Resolve exact IDs from the child-tool schema: prefer `gpt-6-luna`, `gpt-6.1-sol`, `gpt-6-astra` only when exposed. Sol means GPT-6.1 Sol in recommended routes; `gpt-6-sol` and GPT-5.6 models are explicit compatibility choices, not aliases. Use [routing boundaries](references/routing-matrix.md) when a preferred route is absent; do not silently substitute an explicitly required version. A role bound to GPT-6 Sol or GPT-5.6 Luna keeps that exact binding despite its name.
 
 Retire Terra from recommended routes and automatic fallbacks: Sol owns ordinary implementation and investigation. Preserve explicitly pinned models and existing configuration; editing this skill does not authorize rewriting them.
 
-Use the lowest adequate supported effort. Use none only for straightforward extraction/conversion when the host exposes it and checks cover the result; low/medium are the usual starts for tool work. Use xhigh/max for a concrete depth need or an explicit compatible role requirement; ultra only when exposed and justified by the workload, never inferred from API support. Model choice and working role are separate. A role named "explorer" is not proof of sandbox isolation.
+Use the lowest adequate supported effort. GPT-6.1 Sol's API supports low/medium/high/xhigh/max, not none/minimal. Preserve a supported effort when migrating; use low as the starting point for a previously unsupported none/minimal setting and verify representative work. Use none only for straightforward extraction/conversion on a model and host that expose it, such as GPT-6 Luna; low/medium are the usual starts for tool work. Use xhigh/max for a concrete depth need or an explicit compatible role requirement; ultra only when exposed and justified by the workload, never inferred from API support. Model choice and working role are separate. A role named "explorer" is not proof of sandbox isolation.
 
 At dispatch, specify model AND effort when the host permits selection. Otherwise omitted settings may inherit the parent or configured defaults. Prefer a self-contained contract and no history fork; use bounded history only when necessary. Respect full-history/override incompatibilities. Never claim prompt text changed a runtime parameter.