oh-my-opencode 4.17.0 → 4.17.1

package/packages/omo-codex/plugin/components/bootstrap/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"command": "node \"${PLUGIN_ROOT}/components/bootstrap/dist/cli.js\" hook session-start",
 						"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\bootstrap.ps1\"",
 						"timeout": 30,
-						"statusMessage": "(OmO 4.17.0) Checking Bootstrap Provisioning"
+						"statusMessage": "(OmO 4.17.1) Checking Bootstrap Provisioning"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/bootstrap/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sisyphuslabs/codex-bootstrap",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex SessionStart bootstrap component that provisions LazyCodex runtime dependencies from a detached worker.",
 	"type": "module",
 	"private": true,

package/packages/omo-codex/plugin/components/codegraph/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sisyphuslabs/codex-codegraph",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex plugin MCP wrapper for CodeGraph.",
 	"type": "module",
 	"private": true,

package/packages/omo-codex/plugin/components/comment-checker/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 30,
-						"statusMessage": "(OmO 4.17.0) Checking Comments"
+						"statusMessage": "(OmO 4.17.1) Checking Comments"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/comment-checker/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-comment-checker",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex plugin that runs comment-checker after edit-like PostToolUse hooks.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/git-bash/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook pre-tool-use",
 						"timeout": 5,
-						"statusMessage": "(OmO 4.17.0) Recommending Git Bash MCP"
+						"statusMessage": "(OmO 4.17.1) Recommending Git Bash MCP"
 					}
 				]
 			}
@@ -20,7 +20,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
 						"timeout": 5,
-						"statusMessage": "(OmO 4.17.0) Resetting Git Bash MCP Reminder"
+						"statusMessage": "(OmO 4.17.1) Resetting Git Bash MCP Reminder"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/git-bash/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sisyphuslabs/codex-git-bash-hook",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex hook component that reminds Windows sessions to prefer the OMO git_bash MCP.",
 	"type": "module",
 	"private": true,

package/packages/omo-codex/plugin/components/lazycodex-executor-verify/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/components/lazycodex-executor-verify/dist/cli.js\" hook subagent-stop",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Verifying LazyCodex Executor Evidence"
+						"statusMessage": "(OmO 4.17.1) Verifying LazyCodex Executor Evidence"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/lazycodex-executor-verify/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-lazycodex-executor-verify",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex SubagentStop evidence verifier for LazyCodex executor completions.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/lsp/dist/cli.js

@@ -1423,6 +1423,9 @@ async function disposeDefaultLspManager() {
     await m.stopAll();
   }
 }
+function isPlainRecord(value) {
+  return typeof value === "object" && value !== null && !Array.isArray(value);
+}
 function isProcessAlive(pid) {
   if (!Number.isInteger(pid) || pid <= 0)
     return false;
@@ -3313,10 +3316,10 @@ function sendToolCall(socketPath, name, args, timeoutMs) {
   });
 }
 function toToolResult(message) {
-  if (!isRecord6(message) || message["id"] !== REQUEST_ID)
+  if (!isPlainRecord(message) || message["id"] !== REQUEST_ID)
     return null;
   const result = message["result"];
-  if (!isRecord6(result) || !Array.isArray(result["content"]))
+  if (!isPlainRecord(result) || !Array.isArray(result["content"]))
     return null;
   return {
     content: result["content"],
@@ -3324,9 +3327,6 @@ function toToolResult(message) {
     details: result["details"]
   };
 }
-function isRecord6(value) {
-  return typeof value === "object" && value !== null && !Array.isArray(value);
-}
 function errorText(error) {
   return error instanceof Error ? error.message : String(error);
 }
@@ -3450,7 +3450,7 @@ function readSessionState(path) {
       return parsed;
     return emptyState();
   } catch (error) {
-    if (error instanceof SyntaxError || isRecord7(error) && error["code"] === "ENOENT")
+    if (error instanceof SyntaxError || isRecord6(error) && error["code"] === "ENOENT")
       return emptyState();
     throw error;
   }
@@ -3471,12 +3471,12 @@ function safePathSegment(value) {
   return value.replace(/[^A-Za-z0-9._-]/g, "_").slice(0, 120) || "unknown-session";
 }
 function isLspSessionState(value) {
-  if (!isRecord7(value) || !Array.isArray(value["unavailableExtensions"]))
+  if (!isRecord6(value) || !Array.isArray(value["unavailableExtensions"]))
     return false;
   const postCompactProbePending = value["postCompactProbePending"];
   return value["unavailableExtensions"].every((item) => typeof item === "string") && (postCompactProbePending === undefined || typeof postCompactProbePending === "boolean");
 }
-function isRecord7(value) {
+function isRecord6(value) {
   return typeof value === "object" && value !== null && !Array.isArray(value);
 }
 
@@ -3487,7 +3487,7 @@ function extractMutatedFilePaths(input) {
     return [];
   if (isFailedToolResponse(input.tool_response))
     return [];
-  const toolInput = isRecord9(input.tool_input) ? input.tool_input : {};
+  const toolInput = isRecord7(input.tool_input) ? input.tool_input : {};
   const paths = new Set;
   addStringValue(paths, toolInput["path"]);
   addStringValue(paths, toolInput["filePath"]);
@@ -3506,7 +3506,7 @@ function isMutationTool(value) {
   return MUTATION_TOOL_NAMES.has(value.toLowerCase());
 }
 function isFailedToolResponse(value) {
-  if (!isRecord9(value))
+  if (!isRecord7(value))
     return false;
   return value["isError"] === true || value["is_error"] === true || value["error"] === true || value["status"] === "error";
 }
@@ -3549,7 +3549,7 @@ function addPatchFiles(paths, value) {
   if (!Array.isArray(value))
     return;
   for (const item of value) {
-    if (!isRecord9(item))
+    if (!isRecord7(item))
       continue;
     addStringValue(paths, item["path"]);
     addStringValue(paths, item["filePath"]);
@@ -3558,7 +3558,7 @@ function addPatchFiles(paths, value) {
     addStringValue(paths, item["move_path"]);
   }
 }
-function isRecord9(value) {
+function isRecord7(value) {
   return typeof value === "object" && value !== null && !Array.isArray(value);
 }
 
@@ -3742,7 +3742,7 @@ function limitHookText(text2, maxChars) {
 function isCleanDiagnostics(diagnostics) {
   return diagnostics.length === 0 || diagnostics === CLEAN_DIAGNOSTICS_TEXT || diagnostics.startsWith(UNSUPPORTED_EXTENSION_TEXT);
 }
-function isRecord10(value) {
+function isRecord8(value) {
   return typeof value === "object" && value !== null && !Array.isArray(value);
 }
 
@@ -3759,7 +3759,7 @@ async function runHookCli(runHook, stdin) {
     if (!raw.trim())
       return;
     const parsed = JSON.parse(raw);
-    const input = isRecord10(parsed) ? parsed : {};
+    const input = isRecord8(parsed) ? parsed : {};
     const output = await runHook(input);
     if (output)
       process.stdout.write(output);

package/packages/omo-codex/plugin/components/lsp/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 60,
-						"statusMessage": "(OmO 4.17.0) Checking LSP Diagnostics"
+						"statusMessage": "(OmO 4.17.1) Checking LSP Diagnostics"
 					}
 				]
 			}
@@ -21,7 +21,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
 						"timeout": 5,
-						"statusMessage": "(OmO 4.17.0) Resetting LSP Diagnostics Cache"
+						"statusMessage": "(OmO 4.17.1) Resetting LSP Diagnostics Cache"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/lsp/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-lsp",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex plugin that exposes Language Server Protocol tools and post-edit diagnostics.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/rules/bundled-rules/hephaestus/gpt-5.5.md

@@ -45,7 +45,7 @@ Read-only Codex subagent roles live in `CODEX_HOME/agents/`. Spawn: `multi_agent
 
 - `explorer` - codebase search
 - `librarian` - external docs, OSS code, API contracts
-- `plan` - planning for ambiguous, multi-module work
+- `plan` - planning when design is still open after discovery; never for a known checklist or for work being delegated onward
 - `lazycodex-gate-reviewer` - final verification of a finished change
 
 Spawn subagents in parallel for independent investigations; do non-overlapping prep while they run, integrate on return. Never duplicate a running search or poll without a completion signal. While children run, post brief status updates (active subagent count, latest `WORKING:` phase).
@@ -74,7 +74,7 @@ Diagnostics catch type errors, not logic bugs; tests cover only what their autho
 
 # Global Review and Debugging Gate
 
-Before declaring significant work or a PR handoff complete, run `review-work` plus a `debugging` runtime audit; record three debugging hypotheses with runtime evidence each. Timeout, missing deliverable, ack-only, `BLOCKED:`, or inconclusive lanes fail the gate. Redact secrets, tokens, and PII from ledgers, PR bodies, and handoffs.
+Run `review-work` plus a `debugging` runtime audit only before a PR handoff or when the user asks for a review; lane pass/fail semantics live in those skills. For everything else, the gate above is the whole gate: once you have personally observed the artifact working, report your evidence. Redact secrets, tokens, and PII from ledgers, PR bodies, and handoffs.
 
 # Failure Recovery
 

package/packages/omo-codex/plugin/components/rules/bundled-rules/hephaestus/gpt-5.6.md

@@ -33,7 +33,7 @@ Read-only Codex subagent roles live in `CODEX_HOME/agents/`. Spawn: `multi_agent
 
 - `explorer` - codebase search
 - `librarian` - external docs, OSS code, API contracts
-- `plan` - planning for ambiguous, multi-module work
+- `plan` - planning when design is still open after discovery; never for a known checklist or for work being delegated onward
 - `lazycodex-gate-reviewer` - final verification of a finished change
 
 Spawn in parallel for independent investigations; do non-overlapping prep while they run, integrate on return. Never duplicate a running search or poll without a completion signal; post brief status updates while children run (active subagent count, latest `WORKING:` phase).
@@ -50,7 +50,7 @@ Diagnostics catch type errors, not logic bugs; tests cover only what their autho
 
 "This should work" from reading source does not pass. A defect found in usage is yours to fix this turn.
 
-Before declaring significant work or a PR handoff complete, run `review-work` plus a `debugging` runtime audit; record three debugging hypotheses with runtime evidence each. Timeout, missing deliverable, ack-only, `BLOCKED:`, or inconclusive lanes fail the gate. Redact secrets, tokens, and PII from ledgers, PR bodies, and handoffs.
+Run `review-work` plus a `debugging` runtime audit only before a PR handoff or when the user asks for a review; lane pass/fail semantics live in those skills. For everything else, the gate above is the whole gate: once you have personally observed the artifact working, report your evidence. Redact secrets, tokens, and PII from ledgers, PR bodies, and handoffs.
 
 # Failure Recovery
 

package/packages/omo-codex/plugin/components/rules/hooks/hooks.json

@@ -7,7 +7,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook session-start",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Loading Project Rules"
+						"statusMessage": "(OmO 4.17.1) Loading Project Rules"
 					}
 				]
 			}
@@ -19,7 +19,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook user-prompt-submit",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Loading Project Rules"
+						"statusMessage": "(OmO 4.17.1) Loading Project Rules"
 					}
 				]
 			}
@@ -32,7 +32,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Matching Project Rules"
+						"statusMessage": "(OmO 4.17.1) Matching Project Rules"
 					}
 				]
 			}
@@ -45,7 +45,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Resetting Project Rule Cache"
+						"statusMessage": "(OmO 4.17.1) Resetting Project Rule Cache"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/rules/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-rules",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex plugin that injects project rule files into model context through lifecycle hooks.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/start-work-continuation/hooks/hooks.json

@@ -7,7 +7,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook stop",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Checking Start-Work Continuation"
+						"statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation"
 					}
 				]
 			}
@@ -19,7 +19,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook subagent-stop",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Checking Start-Work Continuation"
+						"statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/start-work-continuation/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-start-work-continuation",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex Stop hook continuation injector for omo-codex start-work plans.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/teammode/AGENTS.md

@@ -7,14 +7,14 @@
 Codex team-mode component. Two deliverables in one dir:
 
 - **PostToolUse hook** (`@sisyphuslabs/codex-teammode`): fires after `create_thread` / `codex_app.create_thread`, injects `additionalContext` telling Codex to call `codex_app.set_thread_title` NOW with the real task/role. If the response carries only `pendingWorktreeId`, it instead warns: do NOT `bind-thread` or send the member bootstrap until a real thread id exists.
-- **`teammode` skill**: script-driven orchestration of a named team of Codex workers on ONE immutable transport chosen at init: `multi_agent_v2` (preferred; members are native flat `spawn_agent` agents addressed by `task_name` / `/root/<task_name>` agent path, messaged with `send_message`/`followup_task`) or `codex_app` (fallback; members are app threads addressed by thread id). The leader inspects the active tool list and announces the selected transport to the user BEFORE `init`. Main session is ALWAYS the leader (orchestrates, verifies, integrates - never writes product code); members defined by a concrete part, ownership area, or perspective (`lens`), never job titles. Durable state under `.omo/teams/{session_id}/`: `team.json` + auto-generated `guide.md` member field manual + `artifacts/` exchange dir.
+- **`teammode` skill**: script-driven orchestration of a named team of Codex workers on ONE immutable transport chosen at init: `multi_agent_v2` (preferred; members are native flat `spawn_agent` agents addressed by `task_name` / `/root/<task_name>` agent path, messaged with `send_message`/`followup_task`) or `codex_app` (fallback; members are app threads addressed by thread id). The leader inspects the active tool list (checking `tool_search` for deferred tools when neither set is visible), announces the selected route to the user BEFORE `init`, and when neither set exists announces teammode unavailable and splits the work across plain subagents without creating team state. Main session is ALWAYS the leader (orchestrates, verifies, integrates - never writes product code); members defined by a concrete part, ownership area, or perspective (`lens`), never job titles. Durable state under `.omo/teams/{session_id}/`: `team.json` + auto-generated `guide.md` member field manual + `artifacts/` exchange dir.
 
 ## KEY FILES
 
 - `src/codex-hook.ts` - payload parse, thread/pendingWorktree extraction from object OR JSON-string tool_response, reminder text (ids whitespace-normalized, truncated at 200 chars).
 - `src/cli.ts` - argv dispatch; only `hook post-tool-use`.
 - `hooks/hooks.json` - matcher `^(create_thread|codex_app\.create_thread)$`, runs `node ${PLUGIN_ROOT}/dist/cli.js hook post-tool-use`, timeout 10.
-- `skills/teammode/SKILL.md` - leader protocol: transport selection + pre-init user announcement, team-vs-subagent decision matrix, per-transport create/communicate/worktree/archive flows, ulw-plan parallel-wave mapping, "Let members work - do not rush them" (4-reason message gate; quiet between heartbeats = working, not stalled), archive/delete/stop rules.
+- `skills/teammode/SKILL.md` - leader protocol: transport selection (V2 -> codex_app -> `tool_search` check -> plain-subagent fallback) + pre-init user announcement, V2 spawn schema (`task_name`, `message`, `fork_turns`) with role/tier guidance carried in the bootstrap message, team-vs-subagent decision matrix, per-transport create/communicate/worktree/archive flows, ulw-plan parallel-wave mapping, "Let members work - do not rush them" (4-reason message gate; quiet between heartbeats = working, not stalled), archive/delete/stop rules.
 - `skills/teammode/scripts/team.mjs` - controller CLI: init / add-member / bind-agent / bind-thread / member-prompt / set-status / worktree-add / worktree-remove / integrate / archive / delete / status / guide. Zero npm deps, node builtins only, runs under node or bun on all 3 OSes.
 - `skills/teammode/scripts/team-transport.mjs` - transport identity: `TEAM_TRANSPORTS`, task-name validation (`[a-z0-9_]+`, never `root`), `/root/<task_name>` agent-path derivation, per-operation transport guards.
 - `skills/teammode/scripts/team-state.mjs` - state model + persistence: per-team `.team.lock` dir lock (`owner.json`; `OMO_TEAMMODE_LOCK_TIMEOUT_MS` / `OMO_TEAMMODE_LOCK_RETRY_MS`), atomic tmp+rename writes, symlink- and escape-guarded team dirs, schemaVersion 3 (legacy 2 migrates in memory to `codex_app` and persists on the next mutation), `MIN_MEMBERS = 2`, unique focus/name invariants plus per-transport identity invariants (taskName/agentPath on V2, threadTitle on codex_app).

package/packages/omo-codex/plugin/components/teammode/hooks/hooks.json

@@ -8,7 +8,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
 						"timeout": 10,
-						"statusMessage": "(OmO 4.17.0) Checking Thread Title Hygiene"
+						"statusMessage": "(OmO 4.17.1) Checking Thread Title Hygiene"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/teammode/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@sisyphuslabs/codex-teammode",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex team-mode hook component that keeps background thread titles descriptive after create_thread.",
 	"type": "module",
 	"private": true,

package/packages/omo-codex/plugin/components/teammode/skills/teammode/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: teammode
-description: "Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface and tells the user which transport it selected: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team."
+description: "Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team."
 ---
 
 # Teammode
@@ -40,17 +40,31 @@ Inspect your active tool list and select:
 2. **Codex App threads (fallback)** - select when flat V2 is not available but the
    `codex_app.*` thread tools are (`create_thread`, `read_thread`, `send_message_to_thread`,
    `set_thread_title`, `set_thread_archived`).
-3. **Neither complete set available** - STOP before `init`. Tell the user which tools are
-   missing; do not fake a team with partial tooling.
-
-Then, BEFORE running `init`, tell the user in one line which transport you selected and why,
-e.g. `Teammode transport: MultiAgentV2 (flat spawn_agent with task_name).` or
-`Teammode transport: Codex App threads (flat V2 tools not present in this session).`
-
-Pass that choice to `init` as `--transport multi_agent_v2` or `--transport codex_app`. The
+3. **Neither set visible** - if a `tool_search` tool is active, search for the missing sets
+   (e.g. `spawn_agent`, `codex_app`) before concluding: some environments defer tools behind
+   tool search. A hit is only a lead: revalidate that the visible result is the COMPLETE,
+   mutually compatible transport set from case 1 or 2 before selecting it. Do not combine
+   partial hits from different transports.
+4. **Neither set exists** - teammode cannot run here. Do NOT run `init` or fake a team with
+   partial tooling. If another visible plain-subagent mechanism can independently spawn,
+   communicate with, and observe plain workers, announce that exact mechanism and use it for
+   non-overlapping scopes. Otherwise continue serially and report the capability limitation;
+   never promise or imply plain subagents that this session cannot create.
+
+Then, BEFORE running `init` (or instead of it in case 4), tell the user in one line what this
+environment provides and which route you picked:
+- `Teammode transport: MultiAgentV2 (flat spawn_agent with task_name).`
+- `Teammode transport: Codex App threads (flat V2 tools not present in this session).`
+- `Teammode unavailable: neither MultiAgentV2 nor codex_app tools exist in this session -
+  using <visible plain-subagent mechanism> for independent scopes.`
+- `Teammode unavailable: neither MultiAgentV2 nor codex_app tools exist in this session, and
+  no compatible plain-subagent mechanism is available - continuing serially.`
+
+Pass the choice to `init` as `--transport multi_agent_v2` or `--transport codex_app`. The
 transport is recorded in `team.json` and is IMMUTABLE for the team's lifetime: a V2 spawn
 failure is a V2 blocker to report, never permission to mix Codex App threads into the same
-team. Never probe by trial-calling tools; read your tool list.
+team. Never probe by trial-calling tools; read your tool list, and search it with
+`tool_search` only when a needed set is not visible.
 
 ## You are the leader - orchestrate, do not implement
 
@@ -126,10 +140,13 @@ teams, and a refused command never changes `team.json`.
 **MultiAgentV2 teams:**
 1. If a member needs an isolated worktree, run `worktree-add` BEFORE spawning it - flat
    `spawn_agent` has no cwd argument, so the path must ride in the bootstrap message.
-2. Spawn each member with flat `spawn_agent`: `task_name` is that member's `--task-name`,
-   `message` is the bootstrap printed by `add-member` / `member-prompt`, and
-   `fork_turns: "none"` (members read `guide.md` for context; full parent history is not
-   their context model). Do not set `agent_type`, `model`, or `reasoning_effort`.
+2. Spawn each member with flat `spawn_agent` using only the V2 schema fields:
+   `task_name` is that member's `--task-name`, `message` is the bootstrap printed by
+   `add-member` / `member-prompt`, and `fork_turns` is `"none"` (members read
+   `guide.md` for context; full parent history is not their context model). Put any
+   role, priority, or task-specific routing instruction in `message`; V2 does not accept
+   `agent_type`, `model`, `reasoning_effort`, or `service_tier`, so members inherit the
+   session model.
 3. `bind-agent --agent-path` with the canonical task name the spawn returned (normally
    `/root/<task_name>`); binding confirms the runtime identity matches the roster and records
    the member's cwd. Members are durable: they persist as subagent threads, survive idling,
@@ -272,5 +289,5 @@ is never disbanded is a leak.
 - Member communication stays English unless the user explicitly requests otherwise; user-facing
   replies follow the user's language.
 - Stop if the selected transport's tools (V2 spawn/message/wait/list/interrupt, or Codex App
-  create/read/send/title/archive) are unavailable or stop working; say so instead of faking it
-  or silently switching transports.
+  create/read/send/title/archive) stop working mid-run; say so instead of faking it or silently
+  switching transports. Pre-init absence is not a stop - it routes to the plain-subagent split.

package/packages/omo-codex/plugin/components/teammode/skills/teammode/scripts/team.mjs

@@ -44,6 +44,7 @@ import {
 import { isMultiAgentV2, parseTeamTransport } from "./team-transport.mjs";
 import { addMemberWorktree, integrateMemberBranch, removeMemberWorktree } from "./team-worktree.mjs";
 
+
 function parseFlags(args) {
 	const flags = { _: [] };
 	for (let i = 0; i < args.length; i++) {
@@ -149,7 +150,7 @@ const handlers = {
 			return { team, member: team.members.find((m) => m.id === memberId) };
 		});
 		const delivery = isMultiAgentV2(team)
-			? `Send this as spawn_agent message (task_name "${member.taskName}", fork_turns "none"), then bind-agent --agent-path "${member.agentPath}"`
+			? `Send this with spawn_agent using only task_name "${member.taskName}", message <bootstrap>, and fork_turns "none"; then bind-agent --agent-path "${member.agentPath}"`
 			: `Send this as the new thread's first message (title the thread "${member.threadTitle}")`;
 		process.stdout.write(`added member ${memberId} to team ${sessionId}.\n\n${delivery}:\n---\n${buildMemberPrompt(team, memberId)}\n---\n`);
 	},

package/packages/omo-codex/plugin/components/teammode/test/v2-spawn-schema.test.ts

@@ -0,0 +1,69 @@
+import { describe, expect, it } from "bun:test";
+import { mkdtemp, rm } from "node:fs/promises";
+import { tmpdir } from "node:os";
+import { join } from "node:path";
+import { fileURLToPath } from "node:url";
+
+const teamScriptPath = fileURLToPath(new URL("../skills/teammode/scripts/team.mjs", import.meta.url));
+
+describe("MultiAgentV2 spawn schema", () => {
+	it("#given a team member #when preparing its native spawn #then emits only exposed V2 fields", async () => {
+		// given
+		const root = await mkdtemp(join(tmpdir(), "omo-teammode-v2-schema-"));
+		try {
+			const init = Bun.spawnSync({
+				cmd: [
+					process.execPath,
+					teamScriptPath,
+					"init",
+					"--name",
+					"Schema",
+					"--session-name",
+					"schema",
+					"--session",
+					"schema",
+					"--transport",
+					"multi_agent_v2",
+				],
+				cwd: root,
+				stdout: "pipe",
+				stderr: "pipe",
+			});
+			expect(init.exitCode).toBe(0);
+
+			// when
+			const added = Bun.spawnSync({
+				cmd: [
+					process.execPath,
+					teamScriptPath,
+					"add-member",
+					"--team",
+					"schema",
+					"--id",
+					"A",
+					"--name",
+					"schema-member",
+					"--task-name",
+					"schema_member",
+					"--focus",
+					"spawn schema",
+					"--lens",
+					"area",
+					"--deliverable",
+					"schema contract",
+				],
+				cwd: root,
+				stdout: "pipe",
+				stderr: "pipe",
+			});
+			const delivery = new TextDecoder().decode(added.stdout);
+
+			// then
+			expect(added.exitCode).toBe(0);
+			expect(delivery).toContain('using only task_name "schema_member", message <bootstrap>, and fork_turns "none"');
+			expect(delivery).not.toMatch(/agent_type|model|reasoning_effort|service_tier/);
+		} finally {
+			await rm(root, { force: true, recursive: true });
+		}
+	});
+});

package/packages/omo-codex/plugin/components/telemetry/hooks/hooks.json

@@ -7,7 +7,7 @@
 						"type": "command",
 						"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook session-start",
 						"timeout": 5,
-						"statusMessage": "(OmO 4.17.0) Recording Session Telemetry"
+						"statusMessage": "(OmO 4.17.1) Recording Session Telemetry"
 					}
 				]
 			}

package/packages/omo-codex/plugin/components/telemetry/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@code-yeongyu/codex-telemetry",
-	"version": "4.17.0",
+	"version": "4.17.1",
 	"description": "Codex plugin component that emits omo-codex anonymous daily-active telemetry on SessionStart.",
 	"type": "module",
 	"packageManager": "npm@11.12.1",

package/packages/omo-codex/plugin/components/ultrawork/agents/plan.toml

@@ -1,17 +1,17 @@
 name = "plan"
-description = "Strategic planning consultant. Produces a single executable work plan from a vague or large request. Planner only - never implements. Writes the plan to .omo/plans/<slug>.md."
+description = "Strategic planning consultant for work with unresolved design uncertainty after discovery. Produces one executable plan; never implements. Writes the plan to .omo/plans/<slug>.md."
 nickname_candidates = ["Planner"]
 model = "gpt-5.6-sol"
 model_reasoning_effort = "max"
 
 developer_instructions = """
-Role: strategic planning consultant. You produce a single, bulletproof, executable work plan from a vague or large request.
+Role: strategic planning consultant. You produce a single, bulletproof, executable work plan only when discovery leaves unresolved design uncertainty.
 
 # Identity constraint (NON-NEGOTIABLE)
 You ARE the planner. You ARE NOT an implementer. You read, search, run read-only analysis, and write exactly ONE plan file - never source code, never product builds, never the actual feature. When the caller says "do X / fix X / build X", interpret it as "create a work plan for X". If the caller explicitly demands implementation, REFUSE and answer: "I'm a planner. I produce the work plan. Spawn a worker agent or execute the plan yourself to implement."
 
 # Goal
-Deliver ONE executable plan that a downstream executor can follow with no further interview. Every task is atomic, with explicit references, agent-executable acceptance criteria, QA scenarios, and a commit instruction. (I fit work with 5+ interdependent steps, ambiguous scope, or multiple modules/surfaces. I am the wrong tool for a single-file edit with an obvious pattern, or when the caller already has a plan and just wants execution - say so instead of planning.)
+Deliver ONE executable plan that a downstream executor can follow with no further interview. Every task is atomic, with explicit references, agent-executable acceptance criteria, QA scenarios, and a commit instruction. I fit work whose design remains open after discovery: ambiguous scope, competing decompositions, unclear boundaries, or uncertain dependency ordering. I am the wrong tool for a known checklist however many steps it has, for work the caller is delegating to another session, for a single-file edit with an obvious pattern, or when the caller already has a plan and just wants execution - say so instead of planning.
 
 # Phase 1 - Context gathering (MANDATORY - never plan blind)
 Fire parallel research BEFORE drafting: