oh-my-opencode 5.0.0-beta.8 → 5.0.0-beta.80

package/dist/features/btw-side/tui-session-catalog.d.ts

@@ -0,0 +1,35 @@
+export type BtwCatalogSession = {
+    id: string;
+    title: string;
+    metadata?: Record<string, unknown>;
+    time: {
+        created: number;
+        updated: number;
+    };
+};
+export type BtwSessionCatalog = {
+    main: BtwCatalogSession;
+    sides: BtwCatalogSession[];
+};
+type BtwSessionListInput = {
+    directory: string;
+    roots: false;
+    limit: number;
+};
+type BtwSessionListResponse = {
+    data?: BtwCatalogSession[];
+    error?: unknown;
+};
+type LoadBtwSessionCatalogInput = {
+    currentSessionID: string;
+    directory: string;
+    listSessions: (input: BtwSessionListInput) => Promise<BtwSessionListResponse>;
+    initialLimit?: number;
+    maximumLimit?: number;
+};
+export declare function classifyBtwSessionCatalog(sessions: BtwCatalogSession[], currentSessionID: string): BtwSessionCatalog | undefined;
+export declare function loadBtwSessionCatalog(input: LoadBtwSessionCatalogInput): Promise<{
+    catalog: BtwSessionCatalog | undefined;
+    truncated: boolean;
+}>;
+export {};

package/dist/features/btw-side/tui-side-removal.d.ts

@@ -0,0 +1,11 @@
+export declare function abortBtwSide(args: {
+    sessionID: string;
+    abortSession: (sessionID: string) => Promise<void>;
+    showToast: (message: string) => void;
+}): Promise<void>;
+export declare function deleteBtwSide(args: {
+    sessionID: string;
+    deleteSession: (sessionID: string) => Promise<void>;
+    showToast: (message: string) => void;
+    failureMessage: string;
+}): Promise<boolean>;

package/dist/features/btw-side/tui-side-start.d.ts

@@ -0,0 +1,9 @@
+import type { BtwCreateSessionInput, BtwPromptRef, BtwSideControllerDependencies } from "./tui-controller-types";
+export type PreparedBtwSideStart = {
+    parentSessionID: string;
+    originalDraft: string;
+    consumeDraft: boolean;
+    question: string;
+    createInput: BtwCreateSessionInput;
+};
+export declare function prepareBtwSideStart(dependencies: BtwSideControllerDependencies, promptRef: BtwPromptRef, parentSessionID?: string | undefined): PreparedBtwSideStart | undefined;

package/dist/features/btw-side/tui-wiring.d.ts

@@ -0,0 +1,8 @@
+import type { TuiPluginApi } from "@opencode-ai/plugin/tui";
+type SolidRuntime<Node> = {
+    readonly createElement: (tag: string) => Node;
+    readonly insert: (parent: Node, child: unknown, marker?: unknown, initial?: unknown) => unknown;
+    readonly setProp: (node: Node, name: string, value: unknown, previous?: unknown) => unknown;
+};
+export declare function registerBtwSideTui<Node>(api: TuiPluginApi, solid: SolidRuntime<Node>): Promise<void>;
+export {};

package/dist/features/builtin-commands/templates/hyperplan.d.ts

@@ -1 +1 @@
-export declare const HYPERPLAN_TEMPLATE = "You are running the `/hyperplan` command \u2014 adversarial multi-agent planning via team-mode.\n\nLOAD THE HYPERPLAN SKILL IMMEDIATELY:\n\n```\nskill(name=\"hyperplan\")\n```\n\nAfter loading the skill, follow its 7-phase workflow EXACTLY using this user request.\n\nRoster contract: call `team_create` with category members `unspecified-low`, `unspecified-high`, `ultrabrain`, and `artistry`. Include `deep` only if the category is enabled; if `deep` is disabled or unavailable, retry without only that member and state the degraded roster.\n\n<user-request>\n$ARGUMENTS\n</user-request>\n\nIf team-mode is unavailable (`team_*` tools missing), instruct the user to set `team_mode.enabled: true` in `~/.omo/omo.jsonc` and restart opencode.";
+export declare const HYPERPLAN_TEMPLATE = "You are running the `/hyperplan` command \u2014 adversarial multi-agent planning via team-mode.\n\nLOAD THE HYPERPLAN SKILL IMMEDIATELY:\n\n```\nskill(name=\"hyperplan\")\n```\n\nAfter loading the skill, follow its 7-phase workflow EXACTLY using this user request.\n\nRoster contract: call `team_create` with category members `unspecified-low`, `unspecified-high`, `ultrabrain`, and `artistry`. Include `deep-low` only if the category is enabled; if `deep-low` is disabled or unavailable, retry without only that member and state the degraded roster.\n\n<user-request>\n$ARGUMENTS\n</user-request>\n\nIf team-mode is unavailable (`team_*` tools missing), instruct the user to set `team_mode.enabled: true` in `~/.omo/omo.jsonc` and restart opencode.";

package/dist/features/builtin-commands/templates/refactor-sections/team-mode-addendum.d.ts

@@ -1 +1 @@
-export declare const REFACTOR_TEAM_MODE_ADDENDUM = "\n---\n\n# Team Mode Protocol (active when team_* tools are present)\n\nTeam mode is enabled for this session. The rules below **override Phase 4-6** above. Follow this protocol instead of the in-session step-by-step execution.\n\n## Phase 4 override: Plan agent staffing requirement\n\nWhen invoking the Plan agent in Phase 4.1, append this additional requirement to the prompt:\n\n```\n7. (REQUIRED when team mode is active) Output a Team Staffing Recommendation section with these fields \u2014 missing fields fail Phase 5.0:\n   - total_atomic_steps: integer\n   - file_independent_steps: integer (parallelizable, no cross-file blocker)\n   - cross_file_dependent_steps: integer (has blockers)\n   - per_step_assignment: [{step_id, assigned_to: 'quick' | 'unspecified-low', blockedBy: [step_ids], rationale}]\n   - dispatch_path_recommendation: 'team' | 'legacy' with reason\n   - rationale for the composition\n```\n\n**Classification rules** the plan agent must apply to each step:\n- `quick`: mechanical edits \u2014 LSP rename, extract variable, inline, simple move, signature change without call-site logic.\n- `unspecified-low`: logic-preserving refactors that need reasoning \u2014 extract function, restructure conditional, pattern transformation, cross-file API change.\n- Recommend `team` path when `file_independent_steps >= 3`; recommend `legacy` otherwise.\n\n## Phase 5 override: Dispatch path selection\n\nRead the Team Staffing Recommendation from Phase 4. If any required field is missing, fail here and re-request the plan with the exact missing field names. Do not proceed with a partial plan.\n\nThen choose the path:\n\n- **Team path (5.1-T)**: when the plan recommends `team` AND `file_independent_steps >= 3`. Members execute in parallel, Lead orchestrates, a `deep` verifier lives outside the team.\n- **Legacy path (5.1-L)**: otherwise. Use the original 5.1 / 5.2 / 5.3 flow from above.\n\nRecord the chosen path in the TodoWrite list.\n\n## Phase 5.1-T: `refactor-squad` team execution\n\n**Precondition checks** (fail hard if any step fails):\n\n1. Load the `team-mode` skill via the `skill` tool for lifecycle, message protocol, and limits.\n2. Call `team_list` and verify no active `refactor-squad` run exists; if one does, shutdown + delete the orphan before proceeding.\n3. If `~/.omo/teams/refactor-squad/config.json` is missing, write it using the spec below.\n\n**Team spec** (`~/.omo/teams/refactor-squad/config.json`):\n\n```json\n{\n  \"name\": \"refactor-squad\",\n  \"lead\": { \"kind\": \"subagent_type\", \"subagent_type\": \"sisyphus\" },\n  \"members\": [\n    {\n      \"kind\": \"category\",\n      \"category\": \"quick\",\n      \"prompt\": \"You handle mechanical refactoring steps (LSP rename, extract variable, inline, simple move, signature change). Use LSP tools for correctness. Apply the task description's per-step instructions verbatim \u2014 no scope expansion. After edits, run lsp_diagnostics on touched files. Report via team_send_message(teamRunId=<id>, to=\"lead\", summary=<files touched>, body=<lsp status + diff summary>) + team_task_update(status=completed). Never run tests \u2014 the external verifier handles that. Never git add, never --continue.\"\n    },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    {\n      \"kind\": \"category\",\n      \"category\": \"unspecified-low\",\n      \"prompt\": \"You handle logic-preserving refactors that need reasoning (extract function, restructure conditional, pattern transformation, cross-file API change). Read the task description's plan step carefully. Use the ast-grep skill helper or sg CLI to preview structural rewrites first, review the preview, then execute. If the step is ambiguous or would require out-of-scope changes, STOP and send team_send_message(teamRunId=<id>, to=\"lead\", summary=\"UNCLEAR\", body=<reason>) + team_task_update(status=pending). Same reporting contract as peer quick workers. Never run tests.\"\n    },\n    { \"kind\": \"category\", \"category\": \"unspecified-low\", \"prompt\": \"Same contract as peer unspecified-low worker.\" }\n  ]\n}\n```\n\nRationale for this composition:\n- **4 workers = team mode's parallel cap.** 5+ just queues.\n- **No verifier team member.** Verification needs `deep` reasoning (or `unspecified-high` fallback). In-team category routing downcasts to sisyphus-junior, which is weaker than required \u2014 the verifier runs OUTSIDE the team as a `task(category=\"deep\")`.\n- **quick \u00D7 2** for mechanical edits, **unspecified-low \u00D7 2** for reasoning edits \u2014 mirrors the plan's split.\n\n**Team lifecycle** (one team, reused until Phase 6 cleanup):\n\n1. `team_create(teamName=\"refactor-squad\")`. Record `teamRunId`.\n2. Broadcast the refactor Intent Card ONCE (keep task descriptions slim):\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"refactor-intent\",\n     body=<codemap summary + constraints + established patterns from Phase 2>\n   )\n   ```\n3. Broadcast the verification spec ONCE:\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"verify-spec\",\n     body=<exact test/typecheck/lint commands + expected pass counts + regression indicators from Phase 3.4>\n   )\n   ```\n4. For each plan step, `team_task_create(teamRunId=<id>, subject=\"refactor step <N>: <short>\", description=<per-step instructions from plan, including target files and line ranges, rollback strategy>, blockedBy=<from plan's per_step_assignment>)`.\n\n**Lead monitoring loop**:\n\nWhile any team task is `pending | claimed | in_progress`:\n\n- Wait for `<system-reminder>` or member messages. Avoid tight polling; a single `team_status` check is acceptable if no notification arrives within roughly 10 seconds of expected completion.\n- On a worker completion report, immediately dispatch an **external verifier** \u2014 verification runs OUTSIDE the team because team-member category routing downcasts to sisyphus-junior:\n  ```\n  task(\n    category=\"deep\",\n    load_skills=[],\n    run_in_background=true,\n    description=\"verify step <N>\",\n    prompt=<files touched + verify-spec commands + instruction to return \"PASS\" or \"FAIL:<failing test + specific error + suggested revert hunks>\">\n  )\n  ```\n  If `deep` is unavailable, fall back to `category=\"unspecified-high\"`. Do not create a commit checkpoint until the verifier returns PASS.\n- On a verifier PASS: make the commit checkpoint for that step (see original 5.3). Proceed.\n- On a verifier FAIL: Lead decides:\n  - **Retry with fix hint**: `team_task_update(status=pending)` on the original step + `team_send_message(teamRunId=<id>, to=<original member>, summary=\"retry\", body=<specific failure from verifier>)`. Runtime reassigns.\n  - **Escalate**: after three FAIL cycles on the same step, STOP and consult the user with full evidence.\n- On a member UNCLEAR message: re-harvest context via a targeted `task()` outside the team, broadcast an updated Intent Card fragment, then reassign.\n\nProceed to Phase 6 only when every team task is `completed` AND every paired verifier task returned PASS.\n\n## Phase 6 override: Team cleanup before summary\n\nIf Phase 5 used the team path, dismantle `refactor-squad` BEFORE producing the 6.6 summary. Every exit path \u2014 success, escalation, abort \u2014 must cleanup; orphan teams poison the next session's precondition check.\n\n1. `team_shutdown_request` for each member, then `team_approve_shutdown` if members do not self-approve within a reasonable window.\n2. `team_delete(teamRunId=<id>)`.\n3. `team_list` to confirm no residual `refactor-squad` run.\n\nThe `~/.omo/teams/refactor-squad/config.json` declaration stays on disk; next session reuses it.\n\nAppend to the 6.6 summary a \"Dispatch path\" line and, when team path was used, team metrics (teamRunId, tasks created, verifier runs, team lifetime).\n\n## MUST NOT (team mode)\n\n- Lead never edits files directly \u2014 orchestrate only.\n- Do not inline the Intent Card or verify-spec into task descriptions \u2014 rely on the broadcasts.\n- Do not recreate the team mid-session.\n- Do not run tests from Lead \u2014 the external verifier owns that lane.\n- Do not put `oracle` / `librarian` / `deep` into the team spec \u2014 oracle/librarian are team-ineligible, and `deep` under category routing downcasts to sisyphus-junior. Use them via `task()` outside the team when needed.\n";
+export declare const REFACTOR_TEAM_MODE_ADDENDUM = "\n---\n\n# Team Mode Protocol (active when team_* tools are present)\n\nTeam mode is enabled for this session. The rules below **override Phase 4-6** above. Follow this protocol instead of the in-session step-by-step execution.\n\n## Phase 4 override: Plan agent staffing requirement\n\nWhen invoking the Plan agent in Phase 4.1, append this additional requirement to the prompt:\n\n```\n7. (REQUIRED when team mode is active) Output a Team Staffing Recommendation section with these fields \u2014 missing fields fail Phase 5.0:\n   - total_atomic_steps: integer\n   - file_independent_steps: integer (parallelizable, no cross-file blocker)\n   - cross_file_dependent_steps: integer (has blockers)\n   - per_step_assignment: [{step_id, assigned_to: 'quick' | 'unspecified-low', blockedBy: [step_ids], rationale}]\n   - dispatch_path_recommendation: 'team' | 'legacy' with reason\n   - rationale for the composition\n```\n\n**Classification rules** the plan agent must apply to each step:\n- `quick`: mechanical edits \u2014 LSP rename, extract variable, inline, simple move, signature change without call-site logic.\n- `unspecified-low`: logic-preserving refactors that need reasoning \u2014 extract function, restructure conditional, pattern transformation, cross-file API change.\n- Recommend `team` path when `file_independent_steps >= 3`; recommend `legacy` otherwise.\n\n## Phase 5 override: Dispatch path selection\n\nRead the Team Staffing Recommendation from Phase 4. If any required field is missing, fail here and re-request the plan with the exact missing field names. Do not proceed with a partial plan.\n\nThen choose the path:\n\n- **Team path (5.1-T)**: when the plan recommends `team` AND `file_independent_steps >= 3`. Members execute in parallel, Lead orchestrates, a `deep-high` verifier lives outside the team.\n- **Legacy path (5.1-L)**: otherwise. Use the original 5.1 / 5.2 / 5.3 flow from above.\n\nRecord the chosen path in the TodoWrite list.\n\n## Phase 5.1-T: `refactor-squad` team execution\n\n**Precondition checks** (fail hard if any step fails):\n\n1. Load the `team-mode` skill via the `skill` tool for lifecycle, message protocol, and limits.\n2. Call `team_list` and verify no active `refactor-squad` run exists; if one does, shutdown + delete the orphan before proceeding.\n3. If `~/.omo/teams/refactor-squad/config.json` is missing, write it using the spec below.\n\n**Team spec** (`~/.omo/teams/refactor-squad/config.json`):\n\n```json\n{\n  \"name\": \"refactor-squad\",\n  \"lead\": { \"kind\": \"subagent_type\", \"subagent_type\": \"sisyphus\" },\n  \"members\": [\n    {\n      \"kind\": \"category\",\n      \"category\": \"quick\",\n      \"prompt\": \"You handle mechanical refactoring steps (LSP rename, extract variable, inline, simple move, signature change). Use LSP tools for correctness. Apply the task description's per-step instructions verbatim \u2014 no scope expansion. After edits, run lsp_diagnostics on touched files. Report via team_send_message(teamRunId=<id>, to=\"lead\", summary=<files touched>, body=<lsp status + diff summary>) + team_task_update(status=completed). Never run tests \u2014 the external verifier handles that. Never git add, never --continue.\"\n    },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    {\n      \"kind\": \"category\",\n      \"category\": \"unspecified-low\",\n      \"prompt\": \"You handle logic-preserving refactors that need reasoning (extract function, restructure conditional, pattern transformation, cross-file API change). Read the task description's plan step carefully. Use the ast-grep skill helper or sg CLI to preview structural rewrites first, review the preview, then execute. If the step is ambiguous or would require out-of-scope changes, STOP and send team_send_message(teamRunId=<id>, to=\"lead\", summary=\"UNCLEAR\", body=<reason>) + team_task_update(status=pending). Same reporting contract as peer quick workers. Never run tests.\"\n    },\n    { \"kind\": \"category\", \"category\": \"unspecified-low\", \"prompt\": \"Same contract as peer unspecified-low worker.\" }\n  ]\n}\n```\n\nRationale for this composition:\n- **4 workers = team mode's parallel cap.** 5+ just queues.\n- **No verifier team member.** Verification needs `deep-high` reasoning (or `unspecified-high` fallback). In-team category routing downcasts to sisyphus-junior, which is weaker than required \u2014 the verifier runs OUTSIDE the team as a `task(category=\"deep-high\")`.\n- **quick \u00D7 2** for mechanical edits, **unspecified-low \u00D7 2** for reasoning edits \u2014 mirrors the plan's split.\n\n**Team lifecycle** (one team, reused until Phase 6 cleanup):\n\n1. `team_create(teamName=\"refactor-squad\")`. Record `teamRunId`.\n2. Broadcast the refactor Intent Card ONCE (keep task descriptions slim):\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"refactor-intent\",\n     body=<codemap summary + constraints + established patterns from Phase 2>\n   )\n   ```\n3. Broadcast the verification spec ONCE:\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"verify-spec\",\n     body=<exact test/typecheck/lint commands + expected pass counts + regression indicators from Phase 3.4>\n   )\n   ```\n4. For each plan step, `team_task_create(teamRunId=<id>, subject=\"refactor step <N>: <short>\", description=<per-step instructions from plan, including target files and line ranges, rollback strategy>, blockedBy=<from plan's per_step_assignment>)`.\n\n**Lead monitoring loop**:\n\nWhile any team task is `pending | claimed | in_progress`:\n\n- Wait for `<system-reminder>` or member messages. Avoid tight polling; a single `team_status` check is acceptable if no notification arrives within roughly 10 seconds of expected completion.\n- On a worker completion report, immediately dispatch an **external verifier** \u2014 verification runs OUTSIDE the team because team-member category routing downcasts to sisyphus-junior:\n  ```\n  task(\n    category=\"deep-high\",\n    load_skills=[],\n    run_in_background=true,\n    description=\"verify step <N>\",\n    prompt=<files touched + verify-spec commands + instruction to return \"PASS\" or \"FAIL:<failing test + specific error + suggested revert hunks>\">\n  )\n  ```\n  If `deep-high` is unavailable, fall back to `category=\"unspecified-high\"`. Do not create a commit checkpoint until the verifier returns PASS.\n- On a verifier PASS: make the commit checkpoint for that step (see original 5.3). Proceed.\n- On a verifier FAIL: Lead decides:\n  - **Retry with fix hint**: `team_task_update(status=pending)` on the original step + `team_send_message(teamRunId=<id>, to=<original member>, summary=\"retry\", body=<specific failure from verifier>)`. Runtime reassigns.\n  - **Escalate**: after three FAIL cycles on the same step, STOP and consult the user with full evidence.\n- On a member UNCLEAR message: re-harvest context via a targeted `task()` outside the team, broadcast an updated Intent Card fragment, then reassign.\n\nProceed to Phase 6 only when every team task is `completed` AND every paired verifier task returned PASS.\n\n## Phase 6 override: Team cleanup before summary\n\nIf Phase 5 used the team path, dismantle `refactor-squad` BEFORE producing the 6.6 summary. Every exit path \u2014 success, escalation, abort \u2014 must cleanup; orphan teams poison the next session's precondition check.\n\n1. `team_shutdown_request` for each member, then `team_approve_shutdown` if members do not self-approve within a reasonable window.\n2. `team_delete(teamRunId=<id>)`.\n3. `team_list` to confirm no residual `refactor-squad` run.\n\nThe `~/.omo/teams/refactor-squad/config.json` declaration stays on disk; next session reuses it.\n\nAppend to the 6.6 summary a \"Dispatch path\" line and, when team path was used, team metrics (teamRunId, tasks created, verifier runs, team lifetime).\n\n## MUST NOT (team mode)\n\n- Lead never edits files directly \u2014 orchestrate only.\n- Do not inline the Intent Card or verify-spec into task descriptions \u2014 rely on the broadcasts.\n- Do not recreate the team mid-session.\n- Do not run tests from Lead \u2014 the external verifier owns that lane.\n- Do not put `oracle` / `librarian` / a deep lane into the team spec \u2014 oracle/librarian are team-ineligible, and a deep lane under category routing downcasts to sisyphus-junior. Use them via `task()` outside the team when needed.\n";

package/dist/features/builtin-commands/templates/remove-ai-slops.d.ts

@@ -1,2 +1,2 @@
 export declare const REMOVE_AI_SLOPS_TEMPLATE = "# Remove AI Slops Command\n\n## Codex Harness Tool Compatibility\n\nThis command includes examples for the OpenCode harness. In Codex, do not call OpenCode-only tools such as `call_omo_agent(...)`, `task(...)`, `background_output(...)`, or `team_*(...)` literally. Translate those examples to Codex native tools:\n\n| OpenCode example | Codex tool to use |\n| --- | --- |\n| `call_omo_agent(subagent_type=\"explore\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as an explorer. ...\",\"agent_type\":\"explorer\",\"fork_context\":false})` |\n| `call_omo_agent(subagent_type=\"librarian\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as a librarian. ...\",\"agent_type\":\"librarian\",\"fork_context\":false})` |\n| `task(subagent_type=\"plan\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as a planning agent. ...\",\"agent_type\":\"plan\",\"fork_context\":false})` |\n| `task(subagent_type=\"oracle\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as a rigorous reviewer. ...\",\"agent_type\":\"lazycodex-gate-reviewer\",\"fork_context\":false})` |\n| `task(category=\"...\", ...)` | `multi_agent_v1.spawn_agent({\"message\":\"TASK: act as an implementation or QA worker. ...\",\"fork_context\":false})` |\n| `background_output(task_id=\"...\")` | `multi_agent_v1.wait_agent(...)` for mailbox signals |\n| `team_*(...)` | Use Codex native subagents via `multi_agent_v1.spawn_agent` and `multi_agent_v1.wait_agent`; use `multi_agent_v1.send_input` and `multi_agent_v1.close_agent` only when exposed in the active tools list |\n\nCodex exposes ONE of two subagent tool surfaces per session; check your own tool list and route accordingly. If `multi_agent_v1.*` tools exist, use the table above as written. If instead a flat `spawn_agent` with a required `task_name` exists (`multi_agent_v2`), rewrite every `multi_agent_v1.*` example: `multi_agent_v1.spawn_agent({...,\"fork_context\":false})` becomes `spawn_agent({\"task_name\":\"<lowercase_digits_underscores>\",\"message\":...,\"agent_type\":...,\"fork_turns\":\"none\"})` (`\"all\"` only when full parent history is truly required); `send_input` becomes `send_message`; do not call `close_agent`/`resume_agent` (finished agents end on their own; `followup_task` re-tasks one, `interrupt_agent` stops one); `wait_agent` takes only `timeout_ms` and returns on any child mailbox activity. `agent_type` works the same on both surfaces. If a code block below conflicts with this section, this section wins.\n\nWhen translating `load_skills=[...]`, include the requested skill names in the spawned agent's `message`. If a code block below conflicts with this section, this section wins.\n\n## What this command does\nAnalyzes all files changed in the current branch (compared to parent commit), removes AI-generated code smells in parallel, then critically reviews the changes to ensure safety and behavior preservation. Fixes any issues found during review.\n\n## Step 0: Task Planning\n\nUse TodoWrite to create the task list:\n1. Get changed files from branch\n2. Run $omo:remove-ai-slops on each file in parallel\n3. Critically review all changes\n4. Fix any issues found\n\n## Role Definition\nYou are a senior code quality engineer specialized in identifying and removing AI-generated code patterns while preserving original functionality. You have deep expertise in code review, refactoring safety, and behavioral preservation.\n\n## Process\n\n### Phase 1: Identify Changed Files\nDetect the repository base branch dynamically, then get all changed files in the current branch:\n```bash\nBASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo \"main\")\ngit diff $(git merge-base \"$BASE_BRANCH\" HEAD)..HEAD --name-only\n```\n\nIf `git symbolic-ref refs/remotes/origin/HEAD` is unavailable, detect the base branch at runtime using the repo's configured remote default branch. Only fall back to `main` as a last resort.\n\n### Phase 2: Parallel AI Slop Removal\nFor each changed file, spawn an agent in parallel using the Task tool with the $omo:remove-ai-slops skill:\n\n```\ntask(category=\"quick\", load_skills=[\"remove-ai-slops\"], run_in_background=true, description=\"Remove AI slops from {filename}\", prompt=\"Remove AI slops from: {file_path}\")\n```\n\n**CRITICAL**: Launch ALL agents in a SINGLE message with multiple Task tool calls for maximum parallelism.\n\nBefore running $omo:remove-ai-slops on each file, save a file-specific rollback artifact that captures only the delta introduced by the slop-removal pass. Use a safe pattern such as generating a per-file patch and reverse-applying it if review fails.\n\nDo NOT use `git checkout -- {file_path}` or any rollback that discards pre-existing branch changes in the file.\n\n### Phase 3: Critical Review\nAfter all $omo:remove-ai-slops agents complete, perform a critical review with the following checklist:\n\n**Safety Verification**:\n- [ ] No functional logic was accidentally removed\n- [ ] All error handling is preserved\n- [ ] Type hints remain correct and complete\n- [ ] Import statements are still valid\n- [ ] No breaking changes to public APIs\n\n**Behavior Preservation**:\n- [ ] Return values unchanged\n- [ ] Side effects unchanged\n- [ ] Exception behavior unchanged\n- [ ] Edge case handling preserved\n\n**Code Quality**:\n- [ ] Removed changes are genuinely AI slop (not intentional patterns)\n- [ ] Remaining code follows project conventions\n- [ ] No orphaned code or dead references\n\n### Phase 4: Fix Issues\nIf any issues are found during critical review:\n1. Identify the specific problem\n2. Explain why it's a problem\n3. Revert only the $omo:remove-ai-slops delta using the saved per-file patch or an equivalent reverse-apply workflow\n4. If remaining ai-slops are found after reverting, remove them by editing the file yourself - with parallel tool calls, per-file\n5. Verify the fix doesn't introduce new issues\n\n## Output Format\n\n### Summary Report\n```\n## AI Slop Removal Summary\n\n### Files Processed\n- file1.py: X changes\n- file2.py: Y changes\n\n### Critical Review Results\n- Safety: PASS/FAIL\n- Behavior: PASS/FAIL\n- Quality: PASS/FAIL\n\n### Issues Found & Fixed\n1. [Issue description] -> [Fix applied]\n\n### Final Status\n[CLEAN / ISSUES FIXED / REQUIRES ATTENTION]\n```\n\n## Quality Assurance\n- NEVER remove code that serves a functional purpose\n- ALWAYS verify changes compile/parse correctly\n- ALWAYS preserve test coverage\n- If uncertain about a change, err on the side of keeping the original code";
-export declare const REMOVE_AI_SLOPS_TEAM_MODE_ADDENDUM = "\n---\n\n# Team Mode Protocol (active when team_* tools are present)\n\nTeam mode is enabled for this session. The rules below **override Phase 2-4** of the legacy flow above. Follow this protocol instead of the per-file fire-and-forget `task()` dispatch.\n\n## Phase 2 (team): `slop-squad` setup\n\n**Precondition checks** (fail hard if any step fails):\n\n1. Load the `team-mode` skill via the `skill` tool for lifecycle, message protocol, broadcast rules, 32KB message cap, and 4 parallel worker cap.\n2. Call `team_list` and verify no active run named `slop-squad` exists. If one does, it is an orphan from a crashed prior session \u2014 `team_shutdown_request` + `team_approve_shutdown` + `team_delete` it before proceeding. Do not rename the team or run concurrent sessions under the same name.\n3. If `~/.omo/teams/slop-squad/config.json` is missing, write it using the spec below.\n\n**Team spec** (`~/.omo/teams/slop-squad/config.json`):\n\n```json\n{\n  \"name\": \"slop-squad\",\n  \"lead\": { \"kind\": \"subagent_type\", \"subagent_type\": \"sisyphus\" },\n  \"members\": [\n    {\n      \"kind\": \"category\",\n      \"category\": \"quick\",\n      \"prompt\": \"You run $omo:remove-ai-slops on ONE file per task. Load $omo:remove-ai-slops via the skill tool. Read the task description for the file path. Apply the skill's detection criteria verbatim. After edits: run lsp_diagnostics on the file. Report via team_send_message(teamRunId=<id>, to=\"lead\", summary=<change count>, body=<full $omo:remove-ai-slops report>) + team_task_update(status=completed). On ambiguity: send team_send_message(teamRunId=<id>, to=\"lead\", summary=\"UNCLEAR\", body=<reason>) + team_task_update(status=pending). Never git add, never run tests, never touch other files.\"\n    },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    {\n      \"kind\": \"category\",\n      \"category\": \"unspecified-low\",\n      \"prompt\": \"You are the FIX worker. You claim rework tasks that the lead creates after the external reviewer flags issues. Read the reviewer's per-hunk rollback instructions in the task description, apply the reverse patch, then run $omo:remove-ai-slops ONLY on the non-rolled-back remainder. Same reporting contract as quick peers. Handle UNCLEAR escalations the same way.\"\n    }\n  ]\n}\n```\n\nRationale for this composition:\n- **4 workers = team mode's parallel cap.** A fifth member just queues.\n- **Reviewer is NOT a team member** \u2014 review demands stronger reasoning than category routing provides (team category members are downcast to sisyphus-junior). The reviewer runs OUTSIDE the team as a `deep` task; see Phase 3.\n- **quick \u00D7 3** absorbs the mass of per-file slop removal. **unspecified-low \u00D7 1** is the rework lane for fixes triggered by reviewer findings.\n\n**Team lifecycle** (create once, reuse until Phase 5 cleanup):\n\n1. `team_create(teamName=\"slop-squad\")`. Record `teamRunId` \u2014 every subsequent team call needs it.\n2. Broadcast the detection criteria ONCE so each task description stays minimal:\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"slop-criteria\",\n     body=<the 9 slop categories + KEEP rules; reference the $omo:remove-ai-slops skill content>\n   )\n   ```\n3. Before spawning tasks, save a per-file rollback artifact that captures only the delta the slop-removal pass will introduce. Do NOT use `git checkout -- <file>` \u2014 that would discard pre-existing branch changes.\n4. For each changed file, `team_task_create(teamRunId=<id>, subject=\"slop: <file>\", description=<file path + rollback artifact path + reporting format>, blockedBy=[])`.\n\n## Phase 3 (team): Incremental reviewer dispatch\n\nWhile any team task is `pending | claimed | in_progress`:\n\n- Wait for `<system-reminder>` or member messages. Do NOT tight-poll `team_status`; the runtime notifies on state changes. A single `team_status` check is acceptable if no notification arrives within roughly 10 seconds of expected completion.\n- On each worker completion report:\n  - Log the report to the pending final summary (no blocking).\n  - Immediately dispatch an **external reviewer** \u2014 review runs OUTSIDE the team because team-member category routing downcasts to sisyphus-junior:\n    ```\n    task(\n      category=\"deep\",\n      load_skills=[],\n      run_in_background=true,\n      description=\"slop review: <file>\",\n      prompt=<file path + full worker report + Safety/Behavior/Quality checklist + instruction to output \"PASS\" or \"FAIL:<per-hunk rollback instructions>\">\n    )\n    ```\n    If `deep` is unavailable in this session, fall back to `category=\"unspecified-high\"`.\n- On a reviewer task returning FAIL:\n  - Create a rework team task: `team_task_create(subject=\"rework: <file>\", description=<reverse-patch hunks from reviewer + \"then run $omo:remove-ai-slops on remaining non-rolled-back issues only\">)`. The `unspecified-low` fix member claims it.\n  - Create a new reviewer task paired to the rework completion (same incremental pattern).\n- Loop until every file has a PASS from the reviewer AND no team task is outstanding.\n\n## Phase 4 (team): Fix issues\n\nFixes happen incrementally during Phase 3's loop via rework tasks \u2014 this phase is already handled when the loop exits. Any remaining manual fix that neither worker nor fix member could resolve is handled by Lead here, editing files directly.\n\n## Phase 5 (team): Team cleanup\n\nBefore producing the summary report, dismantle the team on EVERY exit path \u2014 success, escalation, abort \u2014 otherwise the next session's Phase 2 precondition check catches the orphan.\n\n1. `team_shutdown_request` for each member, then `team_approve_shutdown` if members do not self-approve within a reasonable window.\n2. `team_delete(teamRunId=<id>)`.\n3. `team_list` to confirm no residual `slop-squad` run.\n\nThe `~/.omo/teams/slop-squad/config.json` declaration file stays on disk; it is reused next session.\n\n## MUST NOT (team mode)\n\n- Lead never edits files directly \u2014 orchestrate only. If editing is needed, it goes into a team task.\n- Do not inline the full slop-criteria into every task description; rely on the Phase 2 broadcast.\n- Do not call `team_create` again mid-session. One team per resolution.\n- Do not put `oracle` / `librarian` into the team spec \u2014 they are team-ineligible; call them via `task()` outside the team when needed.\n";
+export declare const REMOVE_AI_SLOPS_TEAM_MODE_ADDENDUM = "\n---\n\n# Team Mode Protocol (active when team_* tools are present)\n\nTeam mode is enabled for this session. The rules below **override Phase 2-4** of the legacy flow above. Follow this protocol instead of the per-file fire-and-forget `task()` dispatch.\n\n## Phase 2 (team): `slop-squad` setup\n\n**Precondition checks** (fail hard if any step fails):\n\n1. Load the `team-mode` skill via the `skill` tool for lifecycle, message protocol, broadcast rules, 32KB message cap, and 4 parallel worker cap.\n2. Call `team_list` and verify no active run named `slop-squad` exists. If one does, it is an orphan from a crashed prior session \u2014 `team_shutdown_request` + `team_approve_shutdown` + `team_delete` it before proceeding. Do not rename the team or run concurrent sessions under the same name.\n3. If `~/.omo/teams/slop-squad/config.json` is missing, write it using the spec below.\n\n**Team spec** (`~/.omo/teams/slop-squad/config.json`):\n\n```json\n{\n  \"name\": \"slop-squad\",\n  \"lead\": { \"kind\": \"subagent_type\", \"subagent_type\": \"sisyphus\" },\n  \"members\": [\n    {\n      \"kind\": \"category\",\n      \"category\": \"quick\",\n      \"prompt\": \"You run $omo:remove-ai-slops on ONE file per task. Load $omo:remove-ai-slops via the skill tool. Read the task description for the file path. Apply the skill's detection criteria verbatim. After edits: run lsp_diagnostics on the file. Report via team_send_message(teamRunId=<id>, to=\"lead\", summary=<change count>, body=<full $omo:remove-ai-slops report>) + team_task_update(status=completed). On ambiguity: send team_send_message(teamRunId=<id>, to=\"lead\", summary=\"UNCLEAR\", body=<reason>) + team_task_update(status=pending). Never git add, never run tests, never touch other files.\"\n    },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    { \"kind\": \"category\", \"category\": \"quick\", \"prompt\": \"Same contract as peer quick worker.\" },\n    {\n      \"kind\": \"category\",\n      \"category\": \"unspecified-low\",\n      \"prompt\": \"You are the FIX worker. You claim rework tasks that the lead creates after the external reviewer flags issues. Read the reviewer's per-hunk rollback instructions in the task description, apply the reverse patch, then run $omo:remove-ai-slops ONLY on the non-rolled-back remainder. Same reporting contract as quick peers. Handle UNCLEAR escalations the same way.\"\n    }\n  ]\n}\n```\n\nRationale for this composition:\n- **4 workers = team mode's parallel cap.** A fifth member just queues.\n- **Reviewer is NOT a team member** \u2014 review demands stronger reasoning than category routing provides (team category members are downcast to sisyphus-junior). The reviewer runs OUTSIDE the team as a `deep-high` task; see Phase 3.\n- **quick \u00D7 3** absorbs the mass of per-file slop removal. **unspecified-low \u00D7 1** is the rework lane for fixes triggered by reviewer findings.\n\n**Team lifecycle** (create once, reuse until Phase 5 cleanup):\n\n1. `team_create(teamName=\"slop-squad\")`. Record `teamRunId` \u2014 every subsequent team call needs it.\n2. Broadcast the detection criteria ONCE so each task description stays minimal:\n   ```\n   team_send_message(\n     teamRunId=<id>, to=\"*\", kind=\"announcement\",\n     summary=\"slop-criteria\",\n     body=<the 9 slop categories + KEEP rules; reference the $omo:remove-ai-slops skill content>\n   )\n   ```\n3. Before spawning tasks, save a per-file rollback artifact that captures only the delta the slop-removal pass will introduce. Do NOT use `git checkout -- <file>` \u2014 that would discard pre-existing branch changes.\n4. For each changed file, `team_task_create(teamRunId=<id>, subject=\"slop: <file>\", description=<file path + rollback artifact path + reporting format>, blockedBy=[])`.\n\n## Phase 3 (team): Incremental reviewer dispatch\n\nWhile any team task is `pending | claimed | in_progress`:\n\n- Wait for `<system-reminder>` or member messages. Do NOT tight-poll `team_status`; the runtime notifies on state changes. A single `team_status` check is acceptable if no notification arrives within roughly 10 seconds of expected completion.\n- On each worker completion report:\n  - Log the report to the pending final summary (no blocking).\n  - Immediately dispatch an **external reviewer** \u2014 review runs OUTSIDE the team because team-member category routing downcasts to sisyphus-junior:\n    ```\n    task(\n      category=\"deep-high\",\n      load_skills=[],\n      run_in_background=true,\n      description=\"slop review: <file>\",\n      prompt=<file path + full worker report + Safety/Behavior/Quality checklist + instruction to output \"PASS\" or \"FAIL:<per-hunk rollback instructions>\">\n    )\n    ```\n    If `deep-high` is unavailable in this session, fall back to `category=\"unspecified-high\"`.\n- On a reviewer task returning FAIL:\n  - Create a rework team task: `team_task_create(subject=\"rework: <file>\", description=<reverse-patch hunks from reviewer + \"then run $omo:remove-ai-slops on remaining non-rolled-back issues only\">)`. The `unspecified-low` fix member claims it.\n  - Create a new reviewer task paired to the rework completion (same incremental pattern).\n- Loop until every file has a PASS from the reviewer AND no team task is outstanding.\n\n## Phase 4 (team): Fix issues\n\nFixes happen incrementally during Phase 3's loop via rework tasks \u2014 this phase is already handled when the loop exits. Any remaining manual fix that neither worker nor fix member could resolve is handled by Lead here, editing files directly.\n\n## Phase 5 (team): Team cleanup\n\nBefore producing the summary report, dismantle the team on EVERY exit path \u2014 success, escalation, abort \u2014 otherwise the next session's Phase 2 precondition check catches the orphan.\n\n1. `team_shutdown_request` for each member, then `team_approve_shutdown` if members do not self-approve within a reasonable window.\n2. `team_delete(teamRunId=<id>)`.\n3. `team_list` to confirm no residual `slop-squad` run.\n\nThe `~/.omo/teams/slop-squad/config.json` declaration file stays on disk; it is reused next session.\n\n## MUST NOT (team mode)\n\n- Lead never edits files directly \u2014 orchestrate only. If editing is needed, it goes into a team task.\n- Do not inline the full slop-criteria into every task description; rely on the Phase 2 broadcast.\n- Do not call `team_create` again mid-session. One team per resolution.\n- Do not put `oracle` / `librarian` into the team spec \u2014 they are team-ineligible; call them via `task()` outside the team when needed.\n";

package/dist/features/builtin-commands/templates/ulw-execute.d.ts

@@ -0,0 +1 @@
+export declare const ULW_EXECUTE_TEMPLATE = "You are starting an Atlas work session.\n\n## ARGUMENTS\n\n- `/ulw-execute [plan-name] [--worktree <path>] [--make-pr] [--ship]`\n  - `plan-name` (optional): name or partial match of the plan to start\n  - `--worktree <path>` (optional): absolute path to an existing git worktree to work in\n    - If specified and valid: hook pre-sets worktree_path in boulder.json\n    - If specified but invalid: you must run `git worktree add <path> <branch>` first\n    - If omitted: work directly in the current project directory (no worktree)\n  - `--make-pr` (optional): deliver the work as a pull request. IMPLIES worktree mode - when `--worktree` is omitted, create a task-owned worktree before implementation. On completion push the branch, open a reviewer-readable PR, and hand off with the PR URL (merge only on explicit user ask)\n  - `--ship` (optional): full delivery lifecycle; implies `--make-pr`. After the PR opens, keep working until it is MERGED (CI + review gates, feedback addressed), then clean up the worktree and sync `.omo/` state back\n\n## WHAT TO DO\n\n1. **Find available plans**: Search for Prometheus-generated plan files at `.omo/plans/`\n\n2. **Check for active boulder state**: Read `.omo/boulder.json` if it exists\n\n3. **Decision logic**:\n   - If multiple active works are listed in your context:\n     - This means boulder.json has more than one work with status: `active` or `paused`\n     - Use the Question tool to ask the user which plan to resume\n     - Resume by running `/ulw-execute {plan-name}` for the selected plan\n     - If the user says \"start a new plan\", continue with cold-start auto-selection logic\n   - If exactly one active work is listed and the user did not name a plan:\n     - Auto-resume that single active work\n   - If no active plan OR plan is complete:\n     - List available plan files\n     - If ONE plan: auto-select it\n     - If MULTIPLE plans: show list with timestamps, ask user to select\n\n4. **Worktree Setup** (ONLY when `--worktree` was explicitly specified and `worktree_path` not already set in boulder.json):\n   1. `git worktree list --porcelain` - see available worktrees\n   2. Create: `git worktree add <absolute-path> <branch-or-HEAD>`\n   3. Update boulder.json to add `\"worktree_path\": \"<absolute-path>\"`\n   4. All work happens inside that worktree directory\n\n5. **Create/Update boulder.json**:\n   ```json\n   {\n     \"active_plan\": \"/absolute/path/to/plan.md\",\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"session_ids\": [\"session_id_1\", \"session_id_2\"],\n     \"plan_name\": \"plan-name\",\n     \"worktree_path\": \"/absolute/path/to/git/worktree\"\n   }\n   ```\n\n6. **Read the plan file** and start executing tasks according to atlas workflow\n\n## OUTPUT FORMAT\n\nWhen listing plans for selection:\n```\nAvailable Work Plans\n\nCurrent Time: {ISO timestamp}\nSession ID: {current session id}\n\n1. [plan-name-1.md] - Modified: {date} - Progress: 3/10 tasks\n2. [plan-name-2.md] - Modified: {date} - Progress: 0/5 tasks\n\nWhich plan would you like to work on? (Enter number or plan name)\n```\n\nWhen resuming existing work:\n```\nResuming Work Session\n\nActive Plan: {plan-name}\nProgress: {completed}/{total} tasks\nSessions: {count} (appending current session)\nWorktree: {worktree_path}\n\nReading plan and continuing from last incomplete task...\n```\n\nWhen auto-selecting single plan:\n```\nStarting Work Session\n\nPlan: {plan-name}\nSession ID: {session_id}\nStarted: {timestamp}\nWorktree: {worktree_path}\n\nReading plan and beginning execution...\n```\n\n## CRITICAL\n\n- The session_id is injected by the hook - use it directly\n- Always update boulder.json BEFORE starting work\n- If worktree_path is set in boulder.json, all work happens inside that worktree directory\n- Read the FULL plan file before delegating any tasks\n- Follow atlas delegation protocols (7-section format)\n\n## GOAL + TASK BREAKDOWN (MANDATORY)\n\nDo BOTH of these immediately after reading the plan file, BEFORE starting any work. Skipping either is a defect.\n\n**1. Set the goal, in detail.** When a goal tool is available (`create_goal`), call it with a DETAILED objective: the plan name and path, the concrete end state, the phase/task counts, the delivery mode (direct, `--make-pr`, or `--ship`), and how completion will be verified. One work session = one goal. No goal tool -> record the same objective as the first `.omo/ulw-execute/ledger.jsonl` entry.\n\n**2. Register every phase and task as todos.** Decompose every plan task into granular, implementation-level sub-steps and register ALL of them as task/todo items, grouped phase by phase (one phase per plan wave), BEFORE starting any work. Keep them current at every moment: mark in_progress when work dispatches and done immediately after its verification passes - never batch-complete at the end, never execute work that is not a registered todo. Discovered work is appended as a todo before it runs.\n\n**How to break down**:\n- Each plan checkbox item (e.g., `- [ ] Add user authentication`) must be split into concrete, actionable sub-tasks\n- Sub-tasks should be specific enough that each one touches a clear set of files/functions\n- Include: file to modify, what to change, expected behavior, and how to verify\n- Do NOT leave any task vague - \"implement feature X\" is NOT acceptable; \"add validateToken() to src/auth/middleware.ts that checks JWT expiry and returns 401\" IS acceptable\n\n**Example breakdown**:\nPlan task: `- [ ] Add rate limiting to API`\n\u2192 Todo items:\n  1. Create `src/middleware/rate-limiter.ts` with sliding window algorithm (max 100 req/min per IP)\n  2. Add RateLimiter middleware to `src/app.ts` router chain, before auth middleware\n  3. Add rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) to response in `rate-limiter.ts`\n  4. Add test: verify 429 response after exceeding limit in `src/middleware/rate-limiter.test.ts`\n  5. Add test: verify headers are present on normal responses\n\nRegister these as task/todo items so progress is tracked and visible throughout the session.\n\n## WORKTREE COMPLETION\n\nWhen working in a worktree (`worktree_path` is set in boulder.json) and ALL plan tasks are complete:\n1. Commit all remaining changes in the worktree\n2. **Sync .omo state back**: Copy `.omo/` from the worktree to the main repo before removal.\n   This is CRITICAL when `.omo/` is gitignored - state written during worktree execution would otherwise be lost.\n   ```bash\n   cp -r <worktree-path>/.omo/* <main-repo>/.omo/ 2>/dev/null || true\n   ```\n3. Switch to the main working directory (the original repo, NOT the worktree)\n4. Merge the worktree branch into the current branch: `git merge <worktree-branch>`\n5. If merge succeeds, clean up: `git worktree remove <worktree-path>`\n6. Remove the boulder.json state\n\nThis is the DEFAULT behavior when `--worktree` was used alone. When `--make-pr` or `--ship` is active, skip the local merge and follow the PR Delivery Mode instructions in the session context instead: push the branch and open a PR (`--make-pr` hands off with the PR URL; `--ship` keeps working until the PR is merged), then clean up. Otherwise skip merge only if the user explicitly instructs otherwise (e.g., asks to create a PR instead).";

package/dist/features/builtin-commands/types.d.ts

@@ -1,5 +1,5 @@
 import type { CommandDefinition } from "../claude-code-command-loader";
-export type BuiltinCommandName = "goal" | "refactor" | "start-work" | "stop-continuation" | "handoff" | "remove-ai-slops" | "hyperplan";
+export type BuiltinCommandName = "goal" | "refactor" | "ulw-execute" | "stop-continuation" | "handoff" | "remove-ai-slops" | "hyperplan";
 export interface BuiltinCommandConfig {
     disabled_commands?: BuiltinCommandName[];
 }

package/dist/features/claude-tasks/storage.d.ts

@@ -6,9 +6,14 @@ export declare function resolveTaskListId(config?: Partial<OhMyOpenCodeConfig>):
 export declare function ensureDir(dirPath: string): void;
 export declare function readJsonSafe<T>(filePath: string, schema: z.ZodType<T>): T | null;
 export declare function writeJsonAtomic(filePath: string, data: unknown): void;
+export interface AcquireLockOptions {
+    waitTimeoutMs?: number;
+    retryDelayMs?: number;
+}
+export declare function resolveLockWaitTimeoutMs(): number;
 export declare function generateTaskId(): string;
 export declare function listTaskFiles(config?: Partial<OhMyOpenCodeConfig>): string[];
-export declare function acquireLock(dirPath: string): {
+export declare function acquireLock(dirPath: string, options?: AcquireLockOptions): Promise<{
     acquired: boolean;
     release: () => void;
-};
+}>;

package/dist/features/hook-message-injector/index.d.ts

@@ -2,3 +2,4 @@ export { injectHookMessage, findNearestMessageWithFields, findFirstMessageWithAg
 export type { StoredMessage } from "./injector";
 export type { MessageMeta, OriginalMessageContext, TextPart, ToolPermission } from "./types";
 export { MESSAGE_STORAGE } from "./constants";
+export { generatePartId } from "./id-generation";

package/dist/features/hook-message-injector/sdk-message-lookup.d.ts

@@ -19,6 +19,7 @@ export interface SDKMessage {
         };
         readonly providerID?: string;
         readonly modelID?: string;
+        readonly variant?: string;
         readonly tools?: Record<string, ToolPermission>;
         readonly time?: {
             readonly created?: number;

package/dist/features/monitor/manager-internals.d.ts

@@ -2,7 +2,7 @@ import type { PluginInput } from "@opencode-ai/plugin";
 import type { MonitorConfig } from "../../config/schema/monitor";
 import { registerManagerForCleanup, unregisterManagerForCleanup } from "../background-agent/process-cleanup";
 import { log } from "../../shared";
-import type { InternalPromptDispatchArgs, PromptAsyncInput, PromptDispatchClient } from "../../shared/prompt-async-gate/types";
+import type { InternalPromptDispatchArgs, PromptAsyncInput, PromptDispatchClient } from "@oh-my-opencode/utils/prompt-async-gate/types";
 import { MonitorBatcher, type SchedulerDeps } from "./batcher";
 import { createMonitorPipeline } from "./pipeline";
 import { spawnMonitoredProcess, type MonitoredProcess } from "./process";

package/dist/features/monitor/output-injector-types.d.ts

@@ -1,4 +1,4 @@
-import type { InternalPromptDispatchArgs, InternalPromptDispatchResult, PromptAsyncInput, PromptDispatchClient } from "../../shared/prompt-async-gate/types";
+import type { InternalPromptDispatchArgs, InternalPromptDispatchResult, PromptAsyncInput, PromptDispatchClient } from "@oh-my-opencode/utils/prompt-async-gate/types";
 import type { MonitorRecord, OutputBatch } from "./types";
 export type MonitorPromptClient = PromptDispatchClient & InternalPromptDispatchArgs<PromptAsyncInput>["client"];
 export type MonitorOutputInjectorDeps = {

package/dist/features/opengateway-provider/index.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Injects OpenGateway into opencode's live config so its models appear without
+ * the user hand-writing a provider block.
+ *
+ * opencode activates every `config.provider` entry regardless of credentials, so
+ * the injection is gated on an actual credential: the API key env var, or an
+ * `opengateway` entry in opencode's auth.json. Without one, the config is left
+ * exactly as it came in.
+ */
+export declare const OPENGATEWAY_PROVIDER_ID = "opengateway";
+export declare const OPENGATEWAY_BASE_URL = "https://apis.opengateway.ai/v1";
+export declare const OPENGATEWAY_ENV_VAR = "OPENGATEWAY_API_KEY";
+export declare function applyOpenGatewayProviderConfig(config: Record<string, unknown>): void;

package/dist/features/task-toast-manager/manager.d.ts

@@ -19,39 +19,15 @@ export declare class TaskToastManager {
         skills?: string[];
         modelInfo?: ModelFallbackInfo;
     }): void;
-    /**
-     * Update task status
-     */
     updateTask(id: string, status: TaskStatus): void;
-    /**
-     * Update model info for a task by session ID
-     */
     updateTaskModelBySession(sessionID: string, modelInfo: ModelFallbackInfo): void;
-    /**
-     * Remove completed/error task
-     */
     removeTask(id: string): void;
-    /**
-     * Get all running tasks (newest first)
-     */
     getRunningTasks(): TrackedTask[];
-    /**
-     * Get all queued tasks
-     */
     getQueuedTasks(): TrackedTask[];
-    /**
-     * Format duration since task started
-     */
     private formatDuration;
     private getConcurrencyInfo;
     private buildTaskListMessage;
-    /**
-     * Show consolidated toast with all running/queued tasks
-     */
     private showTaskListToast;
-    /**
-     * Show task completion toast
-     */
     showCompletionToast(task: {
         id: string;
         description: string;

package/dist/features/team-mode/tools/messaging-fallback-wake.d.ts

@@ -0,0 +1,17 @@
+import type { TeamModeConfig } from "../../../config/schema/team-mode";
+import type { RuntimeState } from "@oh-my-opencode/team-core/types";
+import type { LiveDeliveryClient } from "./messaging-live-delivery-client";
+import type { TeamSendMessageDispatchTiming } from "./messaging-runtime";
+type RuntimeMember = RuntimeState["members"][number];
+export declare function enqueueFallbackMailboxWake(input: {
+    readonly client: LiveDeliveryClient;
+    readonly recipientMember: RuntimeMember;
+    readonly recipientSessionId: string;
+    readonly directory: string;
+    readonly teamRunId: string;
+    readonly recipientName: string;
+    readonly messageId: string;
+    readonly config: TeamModeConfig;
+    readonly dispatchTiming?: TeamSendMessageDispatchTiming;
+}): Promise<void>;
+export {};

package/dist/features/team-mode/tools/messaging-live-delivery-recipient.d.ts

@@ -3,6 +3,7 @@ import { buildEnvelope } from "@oh-my-opencode/team-core/team-mailbox/poll";
 import type { Message, RuntimeState } from "@oh-my-opencode/team-core/types";
 import type { LiveDeliveryClient } from "./messaging-live-delivery-client";
 import type { DeliveryReservation } from "./messaging-live-delivery-reservation";
+import type { TeamSendMessageDispatchTiming } from "./messaging-runtime";
 type RuntimeMember = RuntimeState["members"][number];
 type LiveDeliveryEnvelope = ReturnType<typeof buildEnvelope>;
 export declare function deliverLiveToRecipient(input: {
@@ -15,5 +16,7 @@ export declare function deliverLiveToRecipient(input: {
     reservation: DeliveryReservation;
     config: TeamModeConfig;
     directory: string;
+    settleMs?: number;
+    dispatchTiming?: TeamSendMessageDispatchTiming;
 }): Promise<void>;
 export {};

package/dist/features/team-mode/tools/messaging-runtime.d.ts

@@ -7,8 +7,15 @@ export type TeamRuntimeDetails = {
     senderName: string;
     activeMembers: string[];
 };
+export type TeamSendMessageDispatchTiming = {
+    readonly postDispatchHoldMs?: number;
+    readonly queueRetryMs?: number;
+    readonly fallbackWakeSettleMs?: number;
+};
 export type TeamSendMessageToolDeps = {
     loadRuntimeState: typeof loadRuntimeState;
+    liveDeliverySettleMs?: number;
+    dispatchTiming?: TeamSendMessageDispatchTiming;
 };
 export declare const defaultTeamSendMessageToolDeps: TeamSendMessageToolDeps;
 type RuntimeMember = RuntimeState["members"][number];

package/dist/hooks/anthropic-context-window-limit-recovery/message-storage-directory.d.ts

@@ -1,6 +1,3 @@
-import type { PluginInput } from "@opencode-ai/plugin";
 import { getMessageDir } from "../../shared/opencode-message-dir";
 export { getMessageDir };
-type OpencodeClient = PluginInput["client"];
-export declare function getMessageIdsFromSDK(client: OpencodeClient, sessionID: string): Promise<string[]>;
 export declare function getMessageIds(sessionID: string): string[];

package/dist/hooks/anthropic-context-window-limit-recovery/state.d.ts

@@ -2,6 +2,7 @@ import type { AutoCompactState, RetryState, TruncateState } from "./types";
 export declare function getOrCreateRetryState(autoCompactState: AutoCompactState, sessionID: string): RetryState;
 export declare function getOrCreateTruncateState(autoCompactState: AutoCompactState, sessionID: string): TruncateState;
 export declare function clearSessionState(autoCompactState: AutoCompactState, sessionID: string): void;
+export declare function clearAllSessionState(autoCompactState: AutoCompactState): void;
 export declare function setRetryTimer(autoCompactState: AutoCompactState, sessionID: string, timeout: ReturnType<typeof setTimeout>): void;
 export declare function clearRetryTimer(autoCompactState: AutoCompactState, sessionID: string): void;
 export declare function getEmptyContentAttempt(autoCompactState: AutoCompactState, sessionID: string): number;

package/dist/hooks/anthropic-context-window-limit-recovery/storage/empty-messages.d.ts

@@ -1,3 +1,2 @@
 export declare function findEmptyMessages(sessionID: string): string[];
 export declare function findEmptyMessageByIndex(sessionID: string, targetIndex: number): string | null;
-export declare function findFirstEmptyMessage(sessionID: string): string | null;

package/dist/hooks/anthropic-context-window-limit-recovery/tool-result-storage.d.ts

@@ -6,5 +6,16 @@ export declare function truncateToolResult(partPath: string): {
     toolName?: string;
     originalSize?: number;
 };
+/**
+ * Infrastructure for the future distillation feature (issue #1734).
+ *
+ * The non-destructive truncation in `truncateToolResult()` writes the original
+ * tool output to `{partPath}.original`. This function reads that backup so the
+ * distiller can access the full output even after the live part file has been
+ * truncated. It is not called anywhere today because the distillation consumer
+ * has not been implemented yet.
+ */
+export declare function recoverTruncatedOutput(partPath: string): string | null;
+export declare function cleanupTruncationBackups(sessionID: string): number;
 export declare function getTotalToolOutputSize(sessionID: string): number;
 export declare function countTruncatedResults(sessionID: string): number;

package/dist/hooks/atlas/atlas-hook.d.ts

@@ -16,4 +16,5 @@ export declare function createAtlasHook(ctx: PluginInput, options?: AtlasHookOpt
         message?: string;
     }) => Promise<void>;
     "tool.execute.after": (toolInput: import("./types").ToolExecuteAfterInput, toolOutput: import("./types").ToolExecuteAfterOutput | undefined) => Promise<void>;
+    dispose: () => void;
 };

package/dist/hooks/atlas/atlas-lifecycle-store.d.ts

@@ -0,0 +1,50 @@
+import type { PendingTaskRef, SessionState } from "./types";
+export declare const ATLAS_SESSION_STATE_TTL_MS: number;
+export declare const ATLAS_SESSION_PRUNE_INTERVAL_MS: number;
+type PendingAtlasCall = {
+    readonly kind: "file";
+    readonly sessionID?: string;
+    readonly filePath: string;
+    readonly planSnapshot?: string;
+} | {
+    readonly kind: "task";
+    readonly sessionID?: string;
+    readonly task: PendingTaskRef;
+};
+export declare class AtlasLifecycleStore {
+    readonly sessions: Map<string, SessionState>;
+    readonly pendingFilePaths: Map<string, string>;
+    readonly pendingTaskRefs: Map<string, PendingTaskRef>;
+    readonly pendingPlanSnapshots: Map<string, string>;
+    readonly pendingCalls: Map<string, PendingAtlasCall>;
+    readonly sessionCallIDs: Map<string, Set<string>>;
+    private readonly lastAccessedAt;
+    private pruneInterval;
+    private disposed;
+    private readonly disposedState;
+    getExistingState(sessionID: string): SessionState | undefined;
+    getOrCreateState(sessionID: string): SessionState;
+    trackFileCall(callID: string, sessionID: string | undefined, filePath: string): void;
+    trackTaskCall(callID: string, sessionID: string | undefined, task: PendingTaskRef): void;
+    trackPlanSnapshot(callID: string, snapshot: string): void;
+    consumeFileCall(callID: string | undefined): Extract<PendingAtlasCall, {
+        kind: "file";
+    }> | undefined;
+    consumeTaskCall(callID: string | undefined): Extract<PendingAtlasCall, {
+        kind: "task";
+    }> | undefined;
+    clearPendingCall(callID: string | undefined): void;
+    cleanupSession(sessionID: string): void;
+    dispose(): void;
+    get sizes(): {
+        readonly sessions: number;
+        readonly pendingCalls: number;
+        readonly sessionIndexes: number;
+        readonly hasPruneInterval: boolean;
+    };
+    private replaceCall;
+    private removeSessionCallID;
+    private ensurePruneInterval;
+    private prune;
+}
+export {};

package/dist/hooks/atlas/event-handler.d.ts

@@ -5,6 +5,7 @@ export declare function createAtlasEventHandler(input: {
     options?: AtlasHookOptions;
     sessions: Map<string, SessionState>;
     getState: (sessionID: string) => SessionState;
+    cleanupSession: (sessionID: string) => void;
 }): (arg: {
     event: {
         type: string;

package/dist/hooks/atlas/final-wave-approval-gate.test-support.d.ts

@@ -0,0 +1,50 @@
+import { mock } from "bun:test";
+import type { createAtlasHook } from "./index";
+import type { createToolExecuteAfterHandler } from "./tool-execute-after";
+import type { SessionState, ToolExecuteAfterOutput } from "./types";
+type AtlasHookContext = Parameters<typeof createAtlasHook>[0];
+type PromptMock = ReturnType<typeof mock>;
+export type FinalWaveMockPluginInput = AtlasHookContext & {
+    _promptMock: PromptMock;
+};
+export type FinalWaveAfterHandlerHarness = {
+    sessionState: SessionState;
+    run: (toolOutput: ToolExecuteAfterOutput) => Promise<void>;
+};
+/**
+ * Builds a mock plugin input with a recording prompt mock. `resolveParentSessionID`
+ * maps a subagent task session id to the orchestrator session the task belongs to.
+ */
+export declare function createFinalWaveMockPluginInput(options: {
+    directory: string;
+    resolveParentSessionID: (taskSessionID: string) => string;
+}): FinalWaveMockPluginInput;
+/**
+ * Registers per-test temp-directory lifecycle hooks (`.omo` scaffold + boulder state
+ * cleanup) and exposes the current directory. `resetAgentRegistration` also resets
+ * the shared claude-code session-state registry between tests.
+ */
+export declare function registerFinalWaveTestEnvironment(options?: {
+    resetAgentRegistration?: boolean;
+}): {
+    readonly directory: string;
+};
+/** Writes the plan markdown plus the boulder state pointing the session at it. */
+export declare function writeFinalWavePlanState(options: {
+    directory: string;
+    sessionID: string;
+    planName: string;
+    planContent: string;
+}): string;
+/**
+ * Wraps `createToolExecuteAfterHandler` with a shared in-memory session-state map so
+ * tests can assert pause/count flags. The handler factory is passed in explicitly:
+ * suites that mock modules (`mock.module`) must hand over their post-mock import so
+ * the harness runs against the same module instance the suite asserts on.
+ */
+export declare function createFinalWaveAfterHandlerHarness(options: {
+    ctx: AtlasHookContext;
+    sessionID: string;
+    createHandler: typeof createToolExecuteAfterHandler;
+}): FinalWaveAfterHandlerHarness;
+export {};

package/dist/hooks/atlas/system-reminder-templates.d.ts

@@ -2,6 +2,5 @@ export declare const DIRECT_WORK_REMINDER: string;
 export declare const BOULDER_CONTINUATION_PROMPT: string;
 export declare const BOULDER_COMPLETE_PROMPT = "<system-reminder>\nBOULDER COMPLETE: plan \"{PLAN_NAME}\" is fully checked.\n\nTotal elapsed: {ELAPSED_HUMAN}\n\nPer-task breakdown:\n{TASK_BREAKDOWN}\n\nPer your <boulder_completion_response> instructions, print the final ORCHESTRATION COMPLETE summary in your next turn. This nudge fires at most once.\n</system-reminder>";
 export declare const VERIFICATION_REMINDER = "**THE SUBAGENT JUST CLAIMED THIS TASK IS DONE. THEY ARE PROBABLY LYING.**\n\nSubagents say \"done\" when code has errors, tests pass trivially, logic is wrong,\nor they quietly added features nobody asked for. This happens EVERY TIME.\nAssume the work is broken until YOU prove otherwise.\n\n---\n\n**PHASE 1: READ THE CODE FIRST (before running anything)**\n\nDo NOT run tests yet. Read the code FIRST so you know what you're testing.\n\n1. `Bash(\"git diff --stat -- ':!node_modules'\")` - see exactly which files changed. Any file outside expected scope = scope creep.\n2. `Read` EVERY changed file - no exceptions, no skimming.\n3. For EACH file, critically ask:\n   - Does this code ACTUALLY do what the task required? (Re-read the task, compare line by line)\n   - Any stubs, TODOs, placeholders, hardcoded values? (`Grep` for TODO, FIXME, HACK, xxx)\n   - Logic errors? Trace the happy path AND the error path in your head.\n   - Anti-patterns? (`Grep` for `as any`, `@ts-ignore`, empty catch, console.log in changed files)\n   - Scope creep? Did the subagent touch things or add features NOT in the task spec?\n4. Cross-check every claim:\n   - Said \"Updated X\" - READ X. Actually updated, or just superficially touched?\n   - Said \"Added tests\" - READ the tests. Do they test REAL behavior or just `expect(true).toBe(true)`?\n   - Said \"Follows patterns\" - OPEN a reference file. Does it ACTUALLY match?\n\n**If you cannot explain what every changed line does, you have NOT reviewed it.**\n\n**PHASE 2: RUN AUTOMATED CHECKS (targeted, then broad)**\n\nNow that you understand the code, verify mechanically:\n1. `lsp_diagnostics` on EACH changed file - ZERO new errors\n2. Run tests for changed modules FIRST, then full suite\n3. Build/typecheck - exit 0\n\nIf Phase 1 found issues but Phase 2 passes: Phase 2 is WRONG. The code has bugs that tests don't cover. Fix the code.\n\n**PHASE 3: HANDS-ON QA - ACTUALLY RUN IT (MANDATORY for user-facing changes)**\n\nTests and linters CANNOT catch: visual bugs, wrong CLI output, broken user flows, API response shape issues.\n\n**If this task produced anything a user would SEE or INTERACT with, you MUST launch it and verify yourself.**\n\n- **Frontend/UI**: `/playwright` skill - load the page, click through the flow, check console. Verify: page loads, interactions work, console clean, responsive.\n- **TUI/CLI**: `interactive_bash` - run the command, try good input, try bad input, try --help. Verify: command runs, output correct, error messages helpful, edge inputs handled.\n- **API/Backend**: `Bash` with curl - hit the endpoint, check response body, send malformed input. Verify: returns 200, body correct, error cases return proper errors.\n- **Config/Build**: Actually start the service or import the config. Verify: loads without error, backward compatible.\n\nThis is NOT optional \"if applicable\". If the deliverable is user-facing and you did not run it, you are shipping untested work.\n\n**PHASE 4: GATE DECISION - Should you proceed to the next task?**\n\nAnswer honestly:\n1. Can I explain what EVERY changed line does? (If no - back to Phase 1)\n2. Did I SEE it work with my own eyes? (If user-facing and no - back to Phase 3)\n3. Am I confident nothing existing is broken? (If no - run broader tests)\n\nALL three must be YES. \"Probably\" = NO. \"I think so\" = NO. Investigate until CERTAIN.\n\n- **All 3 YES** - Proceed: mark task complete, move to next.\n- **Any NO** - Reject: resume with `task_id`, fix the specific issue.\n- **Unsure** - Reject: \"unsure\" = \"no\". Investigate until you have a definitive answer.\n\n**DO NOT proceed to the next task until all 4 phases are complete and the gate passes.**";
-export declare const VERIFICATION_REMINDER_GEMINI = "**THE SUBAGENT HAS FINISHED. THEIR WORK IS EXTREMELY SUSPICIOUS.**\n\nThe subagent CLAIMS this task is done. Based on thousands of executions, subagent claims are FALSE more often than true.\nThey ROUTINELY:\n- Ship code with syntax errors they didn't bother to check\n- Create stub implementations with TODOs and call it \"done\"\n- Write tests that pass trivially (testing nothing meaningful)\n- Implement logic that does NOT match what was requested\n- Add features nobody asked for and call it \"improvement\"\n- Report \"all tests pass\" when they didn't run any tests\n\n**This is NOT a theoretical warning. This WILL happen on this task. Assume the work is BROKEN.**\n\n**YOU MUST VERIFY WITH ACTUAL TOOL CALLS. NOT REASONING. TOOL CALLS.**\nThinking \"it looks correct\" is NOT verification. Running `lsp_diagnostics` IS.\n\n---\n\n**PHASE 1: READ THE CODE FIRST (DO NOT SKIP - DO NOT RUN TESTS YET)**\n\nRead the code FIRST so you know what you're testing.\n\n1. `Bash(\"git diff --stat -- ':!node_modules'\")` - see exactly which files changed.\n2. `Read` EVERY changed file - no exceptions, no skimming.\n3. For EACH file:\n   - Does this code ACTUALLY do what the task required? RE-READ the task spec.\n   - Any stubs, TODOs, placeholders? `Grep` for TODO, FIXME, HACK, xxx\n   - Anti-patterns? `Grep` for `as any`, `@ts-ignore`, empty catch\n   - Scope creep? Did the subagent add things NOT in the task spec?\n4. Cross-check EVERY claim against actual code.\n\n**If you cannot explain what every changed line does, GO BACK AND READ AGAIN.**\n\n**PHASE 2: RUN AUTOMATED CHECKS**\n\n1. `lsp_diagnostics` on EACH changed file - ZERO new errors. ACTUALLY RUN THIS.\n2. Run tests for changed modules, then full suite. ACTUALLY RUN THESE.\n3. Build/typecheck - exit 0.\n\nIf Phase 1 found issues but Phase 2 passes: Phase 2 is WRONG. Fix the code.\n\n**PHASE 3: HANDS-ON QA (MANDATORY for user-facing changes)**\n\n- **Frontend/UI**: `/playwright`\n- **TUI/CLI**: `interactive_bash`\n- **API/Backend**: `Bash` with curl\n\n**If user-facing and you did not run it, you are shipping UNTESTED BROKEN work.**\n\n**PHASE 4: GATE DECISION**\n\n1. Can I explain what EVERY changed line does? (If no \u2192 Phase 1)\n2. Did I SEE it work via tool calls? (If user-facing and no \u2192 Phase 3)\n3. Am I confident nothing is broken? (If no \u2192 broader tests)\n\nALL three must be YES. \"Probably\" = NO. \"I think so\" = NO.\n\n**DO NOT proceed to the next task until all 4 phases are complete.**";
 export declare const ORCHESTRATOR_DELEGATION_REQUIRED: string;
 export declare const SINGLE_TASK_DIRECTIVE: string;

package/dist/hooks/atlas/tool-execute-before.d.ts

@@ -5,6 +5,9 @@ export declare function createToolExecuteBeforeHandler(input: {
     pendingFilePaths: Map<string, string>;
     pendingTaskRefs: Map<string, PendingTaskRef>;
     pendingPlanSnapshots?: Map<string, string>;
+    trackFileCall?: (callID: string, sessionID: string | undefined, filePath: string) => void;
+    trackTaskCall?: (callID: string, sessionID: string | undefined, task: PendingTaskRef) => void;
+    trackPlanSnapshot?: (callID: string, snapshot: string) => void;
     isCallerOrchestrator?: (sessionID: string | undefined) => Promise<boolean>;
 }): (toolInput: {
     tool: string;

package/dist/hooks/atlas/types.d.ts

@@ -43,6 +43,7 @@ export type PendingTaskRef = {
     task: TrackedTopLevelTaskRef;
 };
 export interface SessionState {
+    lifecycleActive?: boolean;
     lastEventWasAbortError?: boolean;
     skipNextIdleAfterRuntimeErrorRetry?: boolean;
     lastContinuationInjectedAt?: number;

package/dist/hooks/claude-code-hooks/session-hook-state.d.ts

@@ -7,4 +7,5 @@ export declare const sessionInterruptState: Map<string, {
     interrupted: boolean;
 }>;
 export declare function clearSessionHookState(sessionID: string): void;
+export declare function clearSessionEndHookState(sessionID: string): void;
 export declare function clearAllSessionHookState(): void;

package/dist/hooks/claude-code-hooks/stop.d.ts

@@ -2,6 +2,8 @@ import type { ClaudeHooksConfig } from "./types";
 import { type PluginExtendedConfig } from "./config-loader";
 export declare function setStopHookActive(sessionId: string, active: boolean): void;
 export declare function getStopHookActive(sessionId: string): boolean;
+export declare function clearStopHookActive(sessionId: string): void;
+export declare function clearAllStopHookActive(): void;
 export interface StopContext {
     sessionId: string;
     parentSessionId?: string;

package/dist/hooks/claude-code-hooks/todo.d.ts

@@ -8,5 +8,4 @@ export interface OpenCodeTodo {
 }
 export declare function loadTodoFile(sessionId: string): TodoFile | null;
 export declare function saveTodoFile(sessionId: string, file: TodoFile): void;
-export declare function saveOpenCodeTodos(sessionId: string, todos: OpenCodeTodo[]): void;
 export declare function deleteTodoFile(sessionId: string): void;

package/dist/hooks/claude-code-hooks/transcript.d.ts

@@ -1,12 +1,14 @@
 import type { TranscriptEntry } from "./types";
 export declare function getTranscriptPath(sessionId: string): string;
 export declare function appendTranscriptEntry(sessionId: string, entry: TranscriptEntry): void;
+export declare const TRANSCRIPT_CACHE_TTL_MS: number;
 /**
  * Clear transcript cache for a specific session or all sessions.
  * Call on session.deleted to prevent memory accumulation.
  */
 export declare function clearTranscriptCache(sessionId?: string): void;
 export declare function hasTranscriptCacheEntry(sessionId: string): boolean;
+export declare function stopTranscriptCacheCleanup(): void;
 /**
  * Build Claude Code compatible transcript from session messages.
  * Uses per-session cache to avoid redundant session.messages() API calls.

package/dist/hooks/comment-checker/__fixtures__/download-probe.fixture.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/hooks/compaction-context-injector/validated-model.d.ts

@@ -4,9 +4,11 @@ type PromptConfigInfo = {
     model?: {
         providerID?: string;
         modelID?: string;
+        variant?: string;
     };
     providerID?: string;
     modelID?: string;
+    variant?: string;
 };
 export declare function resolveValidatedModel(info: PromptConfigInfo | undefined): CompactionAgentConfigCheckpoint["model"] | undefined;
 export declare function validateCheckpointModel(checkpointModel: CompactionAgentConfigCheckpoint["model"], currentModel: CompactionAgentConfigCheckpoint["model"]): CompactionAgentConfigCheckpoint["model"] | undefined;