oh-my-opencode 4.10.0 → 4.11.0

package/dist/config/index.d.ts

@@ -1,2 +1,2 @@
 export { OhMyOpenCodeConfigSchema, } from "./schema";
-export type { OhMyOpenCodeConfig, AgentOverrideConfig, AgentOverrides, I18nConfig, McpName, AgentName, HookName, BuiltinCommandName, SisyphusAgentConfig, ExperimentalConfig, DynamicContextPruningConfig, DefaultModeConfig, RalphLoopConfig, TmuxConfig, TmuxLayout, SisyphusConfig, SisyphusTasksConfig, RuntimeFallbackConfig, ModelCapabilitiesConfig, FallbackModels, TeamModeConfig, KeywordDetectorConfig, KeywordType, } from "./schema";
+export type { OhMyOpenCodeConfig, AgentOverrideConfig, AgentOverrides, I18nConfig, McpName, AgentName, HookName, BuiltinCommandName, CodegraphConfig, SisyphusAgentConfig, ExperimentalConfig, DynamicContextPruningConfig, DefaultModeConfig, RalphLoopConfig, TmuxConfig, TmuxLayout, SisyphusConfig, SisyphusTasksConfig, RuntimeFallbackConfig, ModelCapabilitiesConfig, FallbackModels, TeamModeConfig, KeywordDetectorConfig, KeywordType, } from "./schema";

package/dist/config/schema/agent-names.d.ts

@@ -16,7 +16,7 @@ export declare const BuiltinSkillNameSchema: z.ZodEnum<{
     playwright: "playwright";
     "agent-browser": "agent-browser";
     "dev-browser": "dev-browser";
-    "frontend-ui-ux": "frontend-ui-ux";
+    frontend: "frontend";
     "git-master": "git-master";
     "review-work": "review-work";
     "remove-ai-slops": "remove-ai-slops";

package/dist/config/schema/codegraph.d.ts

@@ -0,0 +1,9 @@
+import { z } from "zod";
+export declare const CodegraphConfigSchema: z.ZodObject<{
+    auto_provision: z.ZodDefault<z.ZodBoolean>;
+    enabled: z.ZodDefault<z.ZodBoolean>;
+    install_dir: z.ZodOptional<z.ZodString>;
+    telemetry: z.ZodOptional<z.ZodBoolean>;
+    watch_debounce_ms: z.ZodOptional<z.ZodNumber>;
+}, z.core.$strip>;
+export type CodegraphConfig = z.infer<typeof CodegraphConfigSchema>;

package/dist/config/schema/git-env-prefix.d.ts

@@ -1,5 +1 @@
-import { z } from "zod";
-export declare const GIT_ENV_PREFIX_VALIDATION_MESSAGE = "git_env_prefix must be empty or use shell-safe env assignments like \"GIT_MASTER=1\"";
-export declare function isValidGitEnvPrefix(value: string): boolean;
-export declare function assertValidGitEnvPrefix(value: string): string;
-export declare const GitEnvPrefixSchema: z.ZodDefault<z.ZodString>;
+export * from "@oh-my-opencode/skills-loader-core/config/git-env-prefix";

package/dist/config/schema/hooks.d.ts

@@ -18,12 +18,15 @@ export declare const HookNameSchema: z.ZodEnum<{
     "rules-injector": "rules-injector";
     "background-notification": "background-notification";
     "auto-update-checker": "auto-update-checker";
+    "codegraph-bootstrap": "codegraph-bootstrap";
+    "ast-grep-sg-provision": "ast-grep-sg-provision";
     "startup-toast": "startup-toast";
     "keyword-detector": "keyword-detector";
     "agent-usage-reminder": "agent-usage-reminder";
     "non-interactive-env": "non-interactive-env";
     "interactive-bash-session": "interactive-bash-session";
     "tool-pair-validator": "tool-pair-validator";
+    "monitor-status-injector": "monitor-status-injector";
     "category-skill-reminder": "category-skill-reminder";
     "compaction-context-injector": "compaction-context-injector";
     "compaction-todo-preserver": "compaction-todo-preserver";

package/dist/config/schema/monitor.d.ts

@@ -0,0 +1,15 @@
+import { z } from "zod";
+export declare const MonitorConfigSchema: z.ZodObject<{
+    enabled: z.ZodDefault<z.ZodBoolean>;
+    live_mode_enabled: z.ZodDefault<z.ZodBoolean>;
+    allowed_commands: z.ZodOptional<z.ZodArray<z.ZodString>>;
+    max_monitors_per_session: z.ZodDefault<z.ZodNumber>;
+    max_runtime_ms: z.ZodDefault<z.ZodNumber>;
+    batch_max_lines: z.ZodDefault<z.ZodNumber>;
+    batch_max_bytes: z.ZodDefault<z.ZodNumber>;
+    flush_interval_ms: z.ZodDefault<z.ZodNumber>;
+    ring_max_lines: z.ZodDefault<z.ZodNumber>;
+    line_max_bytes: z.ZodDefault<z.ZodNumber>;
+    pattern_max_length: z.ZodDefault<z.ZodNumber>;
+}, z.core.$strip>;
+export type MonitorConfig = z.infer<typeof MonitorConfigSchema>;

package/dist/config/schema/oh-my-opencode-config.d.ts

@@ -7,21 +7,7 @@ export declare const OhMyOpenCodeConfigSchema: z.ZodObject<{
     agent_definitions: z.ZodOptional<z.ZodArray<z.ZodString>>;
     disabled_mcps: z.ZodOptional<z.ZodArray<z.ZodString>>;
     disabled_agents: z.ZodOptional<z.ZodArray<z.ZodString>>;
-    disabled_skills: z.ZodOptional<z.ZodArray<z.ZodEnum<{
-        playwright: "playwright";
-        "agent-browser": "agent-browser";
-        "dev-browser": "dev-browser";
-        "frontend-ui-ux": "frontend-ui-ux";
-        "git-master": "git-master";
-        "review-work": "review-work";
-        "remove-ai-slops": "remove-ai-slops";
-        "init-deep": "init-deep";
-        debugging: "debugging";
-        "security-research": "security-research";
-        "security-review": "security-review";
-        "visual-qa": "visual-qa";
-        "team-mode": "team-mode";
-    }>>>;
+    disabled_skills: z.ZodOptional<z.ZodArray<z.ZodString>>;
     disabled_hooks: z.ZodOptional<z.ZodArray<z.ZodString>>;
     disabled_commands: z.ZodOptional<z.ZodArray<z.ZodEnum<{
         "remove-ai-slops": "remove-ai-slops";
@@ -2319,6 +2305,26 @@ export declare const OhMyOpenCodeConfigSchema: z.ZodObject<{
     i18n: z.ZodOptional<z.ZodObject<{
         locale: z.ZodOptional<z.ZodString>;
     }, z.core.$strip>>;
+    monitor: z.ZodOptional<z.ZodObject<{
+        enabled: z.ZodDefault<z.ZodBoolean>;
+        live_mode_enabled: z.ZodDefault<z.ZodBoolean>;
+        allowed_commands: z.ZodOptional<z.ZodArray<z.ZodString>>;
+        max_monitors_per_session: z.ZodDefault<z.ZodNumber>;
+        max_runtime_ms: z.ZodDefault<z.ZodNumber>;
+        batch_max_lines: z.ZodDefault<z.ZodNumber>;
+        batch_max_bytes: z.ZodDefault<z.ZodNumber>;
+        flush_interval_ms: z.ZodDefault<z.ZodNumber>;
+        ring_max_lines: z.ZodDefault<z.ZodNumber>;
+        line_max_bytes: z.ZodDefault<z.ZodNumber>;
+        pattern_max_length: z.ZodDefault<z.ZodNumber>;
+    }, z.core.$strip>>;
+    codegraph: z.ZodOptional<z.ZodObject<{
+        auto_provision: z.ZodDefault<z.ZodBoolean>;
+        enabled: z.ZodDefault<z.ZodBoolean>;
+        install_dir: z.ZodOptional<z.ZodString>;
+        telemetry: z.ZodOptional<z.ZodBoolean>;
+        watch_debounce_ms: z.ZodOptional<z.ZodNumber>;
+    }, z.core.$strip>>;
     team_mode: z.ZodOptional<z.ZodObject<{
         enabled: z.ZodDefault<z.ZodBoolean>;
         tmux_visualization: z.ZodDefault<z.ZodBoolean>;
@@ -2382,10 +2388,15 @@ export declare const OhMyOpenCodeConfigSchema: z.ZodObject<{
         agent_pane_min_width: z.ZodDefault<z.ZodNumber>;
         isolation: z.ZodDefault<z.ZodEnum<{
             session: "session";
-            inline: "inline";
             window: "window";
+            inline: "inline";
         }>>;
     }, z.core.$strip>>;
+    tui: z.ZodOptional<z.ZodDefault<z.ZodObject<{
+        sidebar: z.ZodDefault<z.ZodObject<{
+            enabled: z.ZodDefault<z.ZodBoolean>;
+        }, z.core.$strip>>;
+    }, z.core.$strip>>>;
     sisyphus: z.ZodOptional<z.ZodObject<{
         tasks: z.ZodOptional<z.ZodObject<{
             storage_path: z.ZodOptional<z.ZodString>;

package/dist/config/schema/openclaw.d.ts

@@ -1,4 +1,5 @@
 import { z } from "zod";
+import type { OpenClawConfig as CoreOpenClawConfig, OpenClawGateway as CoreOpenClawGateway, OpenClawHook as CoreOpenClawHook, OpenClawReplyListenerConfig as CoreOpenClawReplyListenerConfig } from "@oh-my-opencode/openclaw-core";
 export declare const OpenClawGatewaySchema: z.ZodObject<{
     type: z.ZodDefault<z.ZodEnum<{
         command: "command";
@@ -58,7 +59,7 @@ export declare const OpenClawConfigSchema: z.ZodObject<{
         includePrefix: z.ZodDefault<z.ZodBoolean>;
     }, z.core.$strip>>;
 }, z.core.$strip>;
-export type OpenClawConfig = z.infer<typeof OpenClawConfigSchema>;
-export type OpenClawGateway = z.infer<typeof OpenClawGatewaySchema>;
-export type OpenClawHook = z.infer<typeof OpenClawHookSchema>;
-export type OpenClawReplyListenerConfig = z.infer<typeof OpenClawReplyListenerConfigSchema>;
+export type OpenClawConfig = z.infer<typeof OpenClawConfigSchema> & CoreOpenClawConfig;
+export type OpenClawGateway = z.infer<typeof OpenClawGatewaySchema> & CoreOpenClawGateway;
+export type OpenClawHook = z.infer<typeof OpenClawHookSchema> & CoreOpenClawHook;
+export type OpenClawReplyListenerConfig = z.infer<typeof OpenClawReplyListenerConfigSchema> & CoreOpenClawReplyListenerConfig;

package/dist/config/schema/team-mode.d.ts

@@ -1,16 +1 @@
-import { z } from "zod";
-/** Team Mode config - see .omo/plans/team-mode.md (D-01/D-25). */
-export declare const TeamModeConfigSchema: z.ZodObject<{
-    enabled: z.ZodDefault<z.ZodBoolean>;
-    tmux_visualization: z.ZodDefault<z.ZodBoolean>;
-    max_parallel_members: z.ZodDefault<z.ZodNumber>;
-    max_members: z.ZodDefault<z.ZodNumber>;
-    max_messages_per_run: z.ZodDefault<z.ZodNumber>;
-    max_wall_clock_minutes: z.ZodDefault<z.ZodNumber>;
-    max_member_turns: z.ZodDefault<z.ZodNumber>;
-    base_dir: z.ZodOptional<z.ZodString>;
-    message_payload_max_bytes: z.ZodDefault<z.ZodNumber>;
-    recipient_unread_max_bytes: z.ZodDefault<z.ZodNumber>;
-    mailbox_poll_interval_ms: z.ZodDefault<z.ZodNumber>;
-}, z.core.$strip>;
-export type TeamModeConfig = z.infer<typeof TeamModeConfigSchema>;
+export * from "@oh-my-opencode/team-core/config";

package/dist/config/schema/tmux.d.ts

@@ -1,4 +1,5 @@
 import { z } from "zod";
+import type { TmuxConfig, TmuxIsolation, TmuxLayout } from "@oh-my-opencode/tmux-core";
 export declare const TmuxLayoutSchema: z.ZodEnum<{
     "main-horizontal": "main-horizontal";
     "main-vertical": "main-vertical";
@@ -8,8 +9,8 @@ export declare const TmuxLayoutSchema: z.ZodEnum<{
 }>;
 export declare const TmuxIsolationSchema: z.ZodEnum<{
     session: "session";
-    inline: "inline";
     window: "window";
+    inline: "inline";
 }>;
 export declare const TmuxConfigSchema: z.ZodObject<{
     enabled: z.ZodDefault<z.ZodBoolean>;
@@ -25,10 +26,8 @@ export declare const TmuxConfigSchema: z.ZodObject<{
     agent_pane_min_width: z.ZodDefault<z.ZodNumber>;
     isolation: z.ZodDefault<z.ZodEnum<{
         session: "session";
-        inline: "inline";
         window: "window";
+        inline: "inline";
     }>>;
 }, z.core.$strip>;
-export type TmuxConfig = z.infer<typeof TmuxConfigSchema>;
-export type TmuxLayout = z.infer<typeof TmuxLayoutSchema>;
-export type TmuxIsolation = z.infer<typeof TmuxIsolationSchema>;
+export type { TmuxConfig, TmuxIsolation, TmuxLayout };

package/dist/config/schema/tui.d.ts

@@ -0,0 +1,10 @@
+import { z } from "zod";
+export declare const TuiSidebarConfigSchema: z.ZodObject<{
+    enabled: z.ZodDefault<z.ZodBoolean>;
+}, z.core.$strip>;
+export declare const TuiConfigSchema: z.ZodObject<{
+    sidebar: z.ZodDefault<z.ZodObject<{
+        enabled: z.ZodDefault<z.ZodBoolean>;
+    }, z.core.$strip>>;
+}, z.core.$strip>;
+export type TuiConfig = z.infer<typeof TuiConfigSchema>;

package/dist/config/schema.d.ts

@@ -5,6 +5,7 @@ export * from "./schema/background-task";
 export * from "./schema/browser-automation";
 export * from "./schema/categories";
 export * from "./schema/claude-code";
+export * from "./schema/codegraph";
 export * from "./schema/comment-checker";
 export * from "./schema/commands";
 export * from "./schema/default-mode";
@@ -26,5 +27,6 @@ export * from "./schema/skills";
 export * from "./schema/sisyphus";
 export * from "./schema/sisyphus-agent";
 export * from "./schema/tmux";
+export * from "./schema/tui";
 export * from "./schema/websearch";
 export { AnyMcpNameSchema, type AnyMcpName, McpNameSchema, type McpName } from "../mcp/types";

package/dist/config/validate.d.ts

@@ -0,0 +1,8 @@
+import { type OhMyOpenCodeConfig } from "./schema";
+export type PluginConfigValidation = {
+    readonly valid: boolean;
+    readonly messages: readonly string[];
+    readonly path: string | null;
+    readonly config: OhMyOpenCodeConfig;
+};
+export declare function validatePluginConfig(directory: string): PluginConfigValidation;

package/dist/create-hooks.d.ts

@@ -2,6 +2,7 @@ import type { AvailableSkill } from "./agents/dynamic-agent-prompt-builder";
 import type { HookName, OhMyOpenCodeConfig } from "./config";
 import type { LoadedSkill } from "./features/opencode-skill-loader/types";
 import type { BackgroundManager } from "./features/background-agent";
+import type { MonitorManager } from "./features/monitor";
 import type { ModelFallbackControllerAccessor } from "./hooks/model-fallback";
 import type { PluginContext } from "./plugin/types";
 import type { ModelCacheState } from "./plugin-state";
@@ -24,6 +25,7 @@ export declare function createHooks(args: {
     modelCacheState: ModelCacheState;
     backgroundManager: BackgroundManager;
     modelFallbackControllerAccessor?: ModelFallbackControllerAccessor;
+    monitorManager?: MonitorManager;
     isHookEnabled: (hookName: HookName) => boolean;
     safeHookEnabled: boolean;
     mergedSkills: LoadedSkill[];
@@ -45,6 +47,7 @@ export declare function createHooks(args: {
     teamModeStatusInjector: ReturnType<typeof import("./hooks").createTeamModeStatusInjector> | null;
     teamMailboxInjector: ReturnType<typeof import("./hooks").createTeamMailboxInjector> | null;
     toolPairValidator: ReturnType<typeof import("./hooks").createToolPairValidatorHook> | null;
+    monitorStatusInjector: ReturnType<typeof import("./hooks").createMonitorStatusInjectorHook> | null;
     commentChecker: ReturnType<typeof import("./hooks").createCommentCheckerHooks> | null;
     toolOutputTruncator: ReturnType<typeof import("./hooks").createToolOutputTruncatorHook> | null;
     directoryAgentsInjector: ReturnType<typeof import("./hooks").createDirectoryAgentsInjectorHook> | null;
@@ -69,6 +72,8 @@ export declare function createHooks(args: {
     modelFallback: ReturnType<typeof import("./hooks").createModelFallbackHook> | null;
     anthropicContextWindowLimitRecovery: ReturnType<typeof import("./hooks").createAnthropicContextWindowLimitRecoveryHook> | null;
     autoUpdateChecker: ReturnType<typeof import("./hooks").createAutoUpdateCheckerHook> | null;
+    codegraphBootstrap: ReturnType<typeof import("./hooks").createCodegraphBootstrapHook> | null;
+    astGrepSgProvision: ReturnType<typeof import("./hooks").createAstGrepSgProvisionHook> | null;
     agentUsageReminder: ReturnType<typeof import("./hooks").createAgentUsageReminderHook> | null;
     nonInteractiveEnv: ReturnType<typeof import("./hooks").createNonInteractiveEnvHook> | null;
     interactiveBashSession: ReturnType<typeof import("./hooks").createInteractiveBashSessionHook> | null;

package/dist/create-managers.d.ts

@@ -2,8 +2,11 @@ import type { OhMyOpenCodeConfig } from "./config";
 import type { ModelCacheState } from "./plugin-state";
 import type { PluginContext, TmuxConfig } from "./plugin/types";
 import { BackgroundManager } from "./features/background-agent";
+import type { MonitorManager } from "./features/monitor";
+import { createMonitorManager } from "./features/monitor";
 import { SkillMcpManager } from "./features/skill-mcp-manager";
 import { cleanupSessionTeamRuns } from "./features/team-mode/team-runtime/session-cleanup";
+import { TuiStateMirror } from "./features/tui-sidebar/mirror-manager";
 import { initTaskToastManager } from "./features/task-toast-manager";
 import { TmuxSessionManager } from "./features/tmux-subagent";
 import { registerManagerForCleanup } from "./features/background-agent/process-cleanup";
@@ -14,6 +17,8 @@ type CreateManagersDeps = {
     BackgroundManagerClass: typeof BackgroundManager;
     SkillMcpManagerClass: typeof SkillMcpManager;
     TmuxSessionManagerClass: typeof TmuxSessionManager;
+    TuiStateMirrorClass: typeof TuiStateMirror;
+    createMonitorManagerFn: typeof createMonitorManager;
     initTaskToastManagerFn: typeof initTaskToastManager;
     registerManagerForCleanupFn: typeof registerManagerForCleanup;
     cleanupSessionTeamRunsFn: typeof cleanupSessionTeamRuns;
@@ -26,6 +31,8 @@ export type Managers = {
     skillMcpManager: SkillMcpManager;
     configHandler: ReturnType<typeof createConfigHandler>;
     modelFallbackControllerAccessor: ModelFallbackControllerAccessor;
+    tuiStateMirror?: TuiStateMirror;
+    monitorManager?: MonitorManager;
 };
 export declare function createManagers(args: {
     ctx: PluginContext;

package/dist/create-runtime-tmux-config.d.ts

@@ -1,10 +1,10 @@
 import type { OhMyOpenCodeConfig, TmuxConfig } from "./config";
+export { isInteractiveBashEnabled } from "./interactive-bash-availability";
 export declare function isTmuxIntegrationEnabled(pluginConfig: {
     tmux?: {
         enabled?: boolean;
     } | undefined;
 }): boolean;
-export declare function isInteractiveBashEnabled(which?: (binary: string) => string | null): boolean;
 export declare function createRuntimeTmuxConfig(pluginConfig: {
     tmux?: OhMyOpenCodeConfig["tmux"];
 }): TmuxConfig;

package/dist/create-tools.d.ts

@@ -16,6 +16,6 @@ type CreateToolsResult = {
 export declare function createTools(args: {
     ctx: PluginContext;
     pluginConfig: OhMyOpenCodeConfig;
-    managers: Pick<Managers, "backgroundManager" | "tmuxSessionManager" | "skillMcpManager" | "modelFallbackControllerAccessor">;
+    managers: Pick<Managers, "backgroundManager" | "tmuxSessionManager" | "skillMcpManager" | "modelFallbackControllerAccessor" | "monitorManager">;
 }): Promise<CreateToolsResult>;
 export {};

package/dist/features/background-agent/error-classifier.d.ts

@@ -1,4 +1,5 @@
-export declare function isRecord(value: unknown): value is Record<string, unknown>;
+import { isRecord } from "@oh-my-opencode/utils";
+export { isRecord };
 export declare function isAbortedSessionError(error: unknown): boolean;
 export declare function getErrorText(error: unknown): string;
 export declare function extractErrorName(error: unknown): string | undefined;
@@ -8,4 +9,3 @@ interface EventPropertiesLike {
     [key: string]: unknown;
 }
 export declare function getSessionErrorMessage(properties: EventPropertiesLike): string | undefined;
-export {};

package/dist/features/background-agent/manager.d.ts

@@ -4,7 +4,7 @@ import type { ModelFallbackControllerAccessor } from "../../hooks/model-fallback
 import { log } from "../../shared";
 import { type SubagentSpawnContext } from "./subagent-spawn-limits";
 import { TaskHistory } from "./task-history";
-import type { BackgroundTask, LaunchInput, ResumeInput } from "./types";
+import type { BackgroundTask, BackgroundTaskSnapshot, LaunchInput, ResumeInput } from "./types";
 interface EventProperties {
     sessionID?: string;
     info?: {
@@ -102,9 +102,36 @@ export declare class BackgroundManager {
     private processKey;
     private startTask;
     getTask(id: string): BackgroundTask | undefined;
+    getTasksSnapshot(): BackgroundTaskSnapshot[];
     getTasksByParentSession(sessionID: string): BackgroundTask[];
-    /** Return whether a session has direct child background tasks still in flight. */
+    /**
+     * Return whether a session has direct child background tasks still in flight.
+     *
+     * Intentionally checks immediate children only, not all descendants. A
+     * grandchild's completion wake is addressed to its immediate parent session,
+     * never to this ancestor, so blocking on descendants would make the sync poll
+     * loop wait for grandchildren it can never be woken for (returning a stale
+     * pre-grandchild turn after the settle window, or hitting the sync timeout for
+     * long-running descendants). When a deliverable genuinely depends on a
+     * grandchild, the direct child stays running until that grandchild resolves, so
+     * the immediate-child check already covers it; when the child fire-and-forgets
+     * a grandchild, this session correctly does not wait for work it cannot consume.
+     */
     hasActiveChildTasks(sessionID: string): boolean;
+    /**
+     * Return whether a parent-wake notification for this session is queued, scheduled,
+     * mid-dispatch, or dispatched-but-not-yet-consumed. Lets a sync poll loop keep
+     * waiting across the gap between "all children finished" and "the
+     * notification-triggered turn started", instead of declaring the task complete
+     * during that window. The in-flight check is essential: while a wake is being
+     * dispatched the pending entry is already deleted and the dispatched entry is not
+     * yet tracked, so the other three maps would all report false for several seconds.
+     * The notification-preparation check covers the earlier window: a child is marked
+     * terminal (so it no longer counts as active) before the completion path finishes
+     * awaiting its session teardown and queues the wake, so without it the predicate
+     * would report false between the status flip and the wake landing in the pending map.
+     */
+    hasPendingParentWake(sessionID: string): boolean;
     private updateBackgroundTaskMarker;
     getAllDescendantTasks(sessionID: string): BackgroundTask[];
     findBySession(sessionID: string): BackgroundTask | undefined;

package/dist/features/background-agent/parent-wake-dispatched-tracker.d.ts

@@ -7,9 +7,17 @@ export declare class ParentWakeDispatchedTracker {
     private readonly options;
     private dispatchedParentWakes;
     private dispatchedParentWakeTimers;
+    private inFlightDispatches;
+    private notificationPreparations;
     constructor(options: ParentWakeDispatchedTrackerOptions);
     getWakes(): Map<string, PendingParentWake>;
     getTimers(): Map<string, ReturnType<typeof setTimeout>>;
+    markInFlight(sessionID: string): void;
+    clearInFlight(sessionID: string): void;
+    hasInFlight(sessionID: string): boolean;
+    reserveNotificationPreparation(sessionID: string): void;
+    releaseNotificationPreparation(sessionID: string): void;
+    hasNotificationPreparation(sessionID: string): boolean;
     getWake(sessionID: string): PendingParentWake | undefined;
     hasWake(sessionID: string): boolean;
     clearWake(sessionID: string): void;

package/dist/features/background-agent/parent-wake-notifier.d.ts

@@ -11,6 +11,10 @@ export declare class ParentWakeNotifier {
     getPendingParentWakeTimers(): Map<string, ReturnType<typeof setTimeout>>;
     getDispatchedParentWakes(): Map<string, PendingParentWake>;
     getDispatchedParentWakeTimers(): Map<string, ReturnType<typeof setTimeout>>;
+    hasInFlightParentWakeDispatch(sessionID: string): boolean;
+    reserveNotificationPreparation(sessionID: string): void;
+    releaseNotificationPreparation(sessionID: string): void;
+    hasNotificationPreparation(sessionID: string): boolean;
     recordParentSessionActivity(sessionID: string): void;
     queuePendingParentWake(sessionID: string, notification: string, promptContext: ParentWakePromptContext, shouldReply: boolean, delayMs?: number): void;
     flushPendingParentWake(sessionID: string): Promise<void>;

package/dist/features/background-agent/spawner/fallback-agent.d.ts

@@ -1,5 +1,6 @@
+import type { TaskPromptBody } from "./task-prompt-body";
 export declare const FALLBACK_AGENT = "general";
 export declare function isAgentNotFoundError(error: unknown): boolean;
-export declare function buildFallbackBody(originalBody: Record<string, unknown>, fallbackAgent: string, options?: {
+export declare function buildFallbackBody(originalBody: TaskPromptBody, fallbackAgent: string, options?: {
     includeTeamToolDenylist?: boolean;
-}): Record<string, unknown>;
+}): TaskPromptBody;

package/dist/features/background-agent/spawner/task-prompt-body.d.ts

@@ -23,12 +23,11 @@ export type TaskPromptBody = {
     readonly variant?: string;
     readonly system?: string | undefined;
     readonly tools: Record<string, boolean>;
-    readonly parts: readonly [
-        {
-            readonly type: "text";
-            readonly text: string;
-        }
-    ];
+    readonly parts: Array<{
+        readonly type: "text";
+        readonly text: string;
+        readonly synthetic?: boolean;
+    }>;
 };
 export declare function buildTaskPromptBody(options: TaskPromptBodyOptions): TaskPromptBody;
 export {};

package/dist/features/background-agent/task-snapshot.d.ts

@@ -0,0 +1,2 @@
+import type { BackgroundTask, BackgroundTaskSnapshot } from "./types";
+export declare function toBackgroundTaskSnapshots(tasks: Iterable<BackgroundTask>): BackgroundTaskSnapshot[];

package/dist/features/background-agent/types.d.ts

@@ -89,6 +89,13 @@ export interface BackgroundTask {
     /** Number of consecutive polls where session was missing from status map */
     consecutiveMissedPolls?: number;
 }
+export interface BackgroundTaskSnapshot {
+    readonly title: string;
+    readonly status: BackgroundTaskStatus;
+    readonly toolCalls: number | null;
+    readonly lastTool: string | null;
+    readonly agent: string;
+}
 export interface LaunchInput {
     description: string;
     prompt: string;

package/dist/features/builtin-commands/templates/refactor-sections/intro-and-analysis.d.ts

@@ -1 +1 @@
-export declare const REFACTOR_INTRO_AND_ANALYSIS = "# Intelligent Refactor 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\", ...)` | `spawn_agent(agent_type=\"explorer\", task_name=\"...\", message=\"...\")` |\n| `call_omo_agent(subagent_type=\"librarian\", ...)` | `spawn_agent(agent_type=\"librarian\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"plan\", ...)` | `spawn_agent(agent_type=\"plan\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"oracle\", ...)` | `spawn_agent(agent_type=\"codex-ultrawork-reviewer\", task_name=\"...\", message=\"...\")` |\n| `task(category=\"...\", ...)` | `spawn_agent(agent_type=\"worker\", task_name=\"...\", message=\"...\")` |\n| `background_output(task_id=\"...\")` | `wait_agent(...)` to wait for subagent completion and mailbox updates |\n| `team_*(...)` | Use Codex native subagents plus `send_message`, `followup_task`, `wait_agent`, and `close_agent` |\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## Usage\n```\n/refactor <refactoring-target> [--scope=<file|module|project>] [--strategy=<safe|aggressive>]\n\nArguments:\n  refactoring-target: What to refactor. Can be:\n    - File path: src/auth/handler.ts\n    - Symbol name: \"AuthService class\"\n    - Pattern: \"all functions using deprecated API\"\n    - Description: \"extract validation logic into separate module\"\n\nOptions:\n  --scope: Refactoring scope (default: module)\n    - file: Single file only\n    - module: Module/directory scope\n    - project: Entire codebase\n\n  --strategy: Risk tolerance (default: safe)\n    - safe: Conservative, maximum test coverage required\n    - aggressive: Allow broader changes with adequate coverage\n```\n\n## What This Command Does\n\nPerforms intelligent, deterministic refactoring with full codebase awareness. Unlike blind search-and-replace, this command:\n\n1. **Understands your intent** - Analyzes what you actually want to achieve\n2. **Maps the codebase** - Builds a definitive codemap before touching anything\n3. **Assesses risk** - Evaluates test coverage and determines verification strategy\n4. **Plans meticulously** - Creates a detailed plan with Plan agent\n5. **Executes precisely** - Step-by-step refactoring with LSP and AST-grep\n6. **Verifies constantly** - Runs tests after each change to ensure zero regression\n\n---\n\n# PHASE 0: INTENT GATE (MANDATORY FIRST STEP)\n\n**BEFORE ANY ACTION, classify and validate the request.**\n\n## Step 0.1: Parse Request Type\n\n| Signal | Classification | Action |\n|--------|----------------|--------|\n| Specific file/symbol | Explicit | Proceed to codebase analysis |\n| \"Refactor X to Y\" | Clear transformation | Proceed to codebase analysis |\n| \"Improve\", \"Clean up\" | Open-ended | **MUST ask**: \"What specific improvement?\" |\n| Ambiguous scope | Uncertain | **MUST ask**: \"Which modules/files?\" |\n| Missing context | Incomplete | **MUST ask**: \"What's the desired outcome?\" |\n\n## Step 0.2: Validate Understanding\n\nBefore proceeding, confirm:\n- [ ] Target is clearly identified\n- [ ] Desired outcome is understood\n- [ ] Scope is defined (file/module/project)\n- [ ] Success criteria can be articulated\n\n**If ANY of above is unclear, ASK CLARIFYING QUESTION:**\n\n```\nI want to make sure I understand the refactoring goal correctly.\n\n**What I understood**: [interpretation]\n**What I'm unsure about**: [specific ambiguity]\n\nOptions I see:\n1. [Option A] - [implications]\n2. [Option B] - [implications]\n\n**My recommendation**: [suggestion with reasoning]\n\nShould I proceed with [recommendation], or would you prefer differently?\n```\n\n## Step 0.3: Create Initial Todos\n\n**IMMEDIATELY after understanding the request, create todos:**\n\n```\nTodoWrite([\n  {\"id\": \"phase-1\", \"content\": \"PHASE 1: Codebase Analysis - launch parallel explore agents\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-2\", \"content\": \"PHASE 2: Build Codemap - map dependencies and impact zones\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-3\", \"content\": \"PHASE 3: Test Assessment - analyze test coverage and verification strategy\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-4\", \"content\": \"PHASE 4: Plan Generation - invoke Plan agent for detailed refactoring plan\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-5\", \"content\": \"PHASE 5: Execute Refactoring - step-by-step with continuous verification\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-6\", \"content\": \"PHASE 6: Final Verification - full test suite and regression check\", \"status\": \"pending\", \"priority\": \"high\"}\n])\n```\n\n---\n\n# PHASE 1: CODEBASE ANALYSIS (PARALLEL EXPLORATION)\n\n**Mark phase-1 as in_progress.**\n\n## 1.1: Launch Parallel Explore Agents (BACKGROUND)\n\nFire ALL of these simultaneously using `call_omo_agent`:\n\n```\n// Agent 1: Find the refactoring target\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find all occurrences and definitions of [TARGET]. \n  Report: file paths, line numbers, usage patterns.\"\n)\n\n// Agent 2: Find related code\ncall_omo_agent(\n  subagent_type=\"explore\", \n  run_in_background=true,\n  prompt=\"Find all code that imports, uses, or depends on [TARGET].\n  Report: dependency chains, import graphs.\"\n)\n\n// Agent 3: Find similar patterns\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find similar code patterns to [TARGET] in the codebase.\n  Report: analogous implementations, established conventions.\"\n)\n\n// Agent 4: Find tests\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find all test files related to [TARGET].\n  Report: test file paths, test case names, coverage indicators.\"\n)\n\n// Agent 5: Architecture context\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find architectural patterns and module organization around [TARGET].\n  Report: module boundaries, layer structure, design patterns in use.\"\n)\n```\n\n## 1.2: Direct Tool Exploration (WHILE AGENTS RUN)\n\nWhile background agents are running, use direct tools:\n\n### LSP Tools for Precise Analysis:\n\n```typescript\n// Find definition(s)\nLspGotoDefinition(filePath, line, character)  // Where is it defined?\n\n// Find ALL usages across workspace\nLspFindReferences(filePath, line, character, includeDeclaration=true)\n\n// Get file structure\nLspDocumentSymbols(filePath)  // Hierarchical outline\nLspWorkspaceSymbols(filePath, query=\"[target_symbol]\")  // Search by name\n\n// Get current diagnostics\nlsp_diagnostics(filePath)  // Errors, warnings before we start\n```\n\n### AST-Grep for Pattern Analysis:\n\n```typescript\n// Find structural patterns\nast_grep_search(\n  pattern=\"function $NAME($$$) { $$$ }\",  // or relevant pattern\n  lang=\"typescript\",  // or relevant language\n  paths=[\"src/\"]\n)\n\n// Preview refactoring (DRY RUN)\nast_grep_replace(\n  pattern=\"[old_pattern]\",\n  rewrite=\"[new_pattern]\",\n  lang=\"[language]\",\n  dryRun=true  // ALWAYS preview first\n)\n```\n\n### Grep for Text Patterns:\n\n```\ngrep(pattern=\"[search_term]\", path=\"src/\", include=\"*.ts\")\n```\n\n## 1.3: Collect Background Results\n\n```\nbackground_output(task_id=\"[agent_1_id]\")\nbackground_output(task_id=\"[agent_2_id]\")\n...\n```\n\n**Mark phase-1 as completed after all results collected.**\n\n---\n\n";
+export declare const REFACTOR_INTRO_AND_ANALYSIS = "# Intelligent Refactor 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\", ...)` | `spawn_agent(agent_type=\"explorer\", task_name=\"...\", message=\"...\")` |\n| `call_omo_agent(subagent_type=\"librarian\", ...)` | `spawn_agent(agent_type=\"librarian\", task_name=\"...\", message=\"...\")` |\n| `task(subagent_type=\"plan\", ...)` | `spawn_agent(agent_type=\"plan\", task_name=\"...\", message=\"...\")` |\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=\"...\", ...)` | `spawn_agent(agent_type=\"worker\", task_name=\"...\", message=\"...\")` |\n| `background_output(task_id=\"...\")` | `wait_agent(...)` to wait for subagent completion and mailbox updates |\n| `team_*(...)` | Use Codex native subagents plus `send_message`, `followup_task`, `wait_agent`, and `close_agent` |\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## Usage\n```\n/refactor <refactoring-target> [--scope=<file|module|project>] [--strategy=<safe|aggressive>]\n\nArguments:\n  refactoring-target: What to refactor. Can be:\n    - File path: src/auth/handler.ts\n    - Symbol name: \"AuthService class\"\n    - Pattern: \"all functions using deprecated API\"\n    - Description: \"extract validation logic into separate module\"\n\nOptions:\n  --scope: Refactoring scope (default: module)\n    - file: Single file only\n    - module: Module/directory scope\n    - project: Entire codebase\n\n  --strategy: Risk tolerance (default: safe)\n    - safe: Conservative, maximum test coverage required\n    - aggressive: Allow broader changes with adequate coverage\n```\n\n## What This Command Does\n\nPerforms intelligent, deterministic refactoring with full codebase awareness. Unlike blind search-and-replace, this command:\n\n1. **Understands your intent** - Analyzes what you actually want to achieve\n2. **Maps the codebase** - Builds a definitive codemap before touching anything\n3. **Assesses risk** - Evaluates test coverage and determines verification strategy\n4. **Plans meticulously** - Creates a detailed plan with Plan agent\n5. **Executes precisely** - Step-by-step refactoring with LSP and AST-grep\n6. **Verifies constantly** - Runs tests after each change to ensure zero regression\n\n---\n\n# PHASE 0: INTENT GATE (MANDATORY FIRST STEP)\n\n**BEFORE ANY ACTION, classify and validate the request.**\n\n## Step 0.1: Parse Request Type\n\n| Signal | Classification | Action |\n|--------|----------------|--------|\n| Specific file/symbol | Explicit | Proceed to codebase analysis |\n| \"Refactor X to Y\" | Clear transformation | Proceed to codebase analysis |\n| \"Improve\", \"Clean up\" | Open-ended | **MUST ask**: \"What specific improvement?\" |\n| Ambiguous scope | Uncertain | **MUST ask**: \"Which modules/files?\" |\n| Missing context | Incomplete | **MUST ask**: \"What's the desired outcome?\" |\n\n## Step 0.2: Validate Understanding\n\nBefore proceeding, confirm:\n- [ ] Target is clearly identified\n- [ ] Desired outcome is understood\n- [ ] Scope is defined (file/module/project)\n- [ ] Success criteria can be articulated\n\n**If ANY of above is unclear, ASK CLARIFYING QUESTION:**\n\n```\nI want to make sure I understand the refactoring goal correctly.\n\n**What I understood**: [interpretation]\n**What I'm unsure about**: [specific ambiguity]\n\nOptions I see:\n1. [Option A] - [implications]\n2. [Option B] - [implications]\n\n**My recommendation**: [suggestion with reasoning]\n\nShould I proceed with [recommendation], or would you prefer differently?\n```\n\n## Step 0.3: Create Initial Todos\n\n**IMMEDIATELY after understanding the request, create todos:**\n\n```\nTodoWrite([\n  {\"id\": \"phase-1\", \"content\": \"PHASE 1: Codebase Analysis - launch parallel explore agents\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-2\", \"content\": \"PHASE 2: Build Codemap - map dependencies and impact zones\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-3\", \"content\": \"PHASE 3: Test Assessment - analyze test coverage and verification strategy\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-4\", \"content\": \"PHASE 4: Plan Generation - invoke Plan agent for detailed refactoring plan\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-5\", \"content\": \"PHASE 5: Execute Refactoring - step-by-step with continuous verification\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"phase-6\", \"content\": \"PHASE 6: Final Verification - full test suite and regression check\", \"status\": \"pending\", \"priority\": \"high\"}\n])\n```\n\n---\n\n# PHASE 1: CODEBASE ANALYSIS (PARALLEL EXPLORATION)\n\n**Mark phase-1 as in_progress.**\n\n## 1.1: Launch Parallel Explore Agents (BACKGROUND)\n\nFire ALL of these simultaneously using `call_omo_agent`:\n\n```\n// Agent 1: Find the refactoring target\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find all occurrences and definitions of [TARGET]. \n  Report: file paths, line numbers, usage patterns.\"\n)\n\n// Agent 2: Find related code\ncall_omo_agent(\n  subagent_type=\"explore\", \n  run_in_background=true,\n  prompt=\"Find all code that imports, uses, or depends on [TARGET].\n  Report: dependency chains, import graphs.\"\n)\n\n// Agent 3: Find similar patterns\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find similar code patterns to [TARGET] in the codebase.\n  Report: analogous implementations, established conventions.\"\n)\n\n// Agent 4: Find tests\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find all test files related to [TARGET].\n  Report: test file paths, test case names, coverage indicators.\"\n)\n\n// Agent 5: Architecture context\ncall_omo_agent(\n  subagent_type=\"explore\",\n  run_in_background=true,\n  prompt=\"Find architectural patterns and module organization around [TARGET].\n  Report: module boundaries, layer structure, design patterns in use.\"\n)\n```\n\n## 1.2: Direct Tool Exploration (WHILE AGENTS RUN)\n\nWhile background agents are running, use direct tools:\n\n### LSP Tools for Precise Analysis:\n\n```typescript\n// Find definition(s)\nLspGotoDefinition(filePath, line, character)  // Where is it defined?\n\n// Find ALL usages across workspace\nLspFindReferences(filePath, line, character, includeDeclaration=true)\n\n// Get file structure\nLspDocumentSymbols(filePath)  // Hierarchical outline\nLspWorkspaceSymbols(filePath, query=\"[target_symbol]\")  // Search by name\n\n// Get current diagnostics\nlsp_diagnostics(filePath)  // Errors, warnings before we start\n```\n\n### AST-Grep Skill for Pattern Analysis:\n\n```bash\n// Find structural patterns\npython3 scripts/ast_grep_helper.py search 'function $NAME($$$) { $$$ }' --lang ts src/\n\n# Preview refactoring first\nsg --pattern '[old_pattern]' --rewrite '[new_pattern]' --lang ts src/\n```\n\n### Grep for Text Patterns:\n\n```\ngrep(pattern=\"[search_term]\", path=\"src/\", include=\"*.ts\")\n```\n\n## 1.3: Collect Background Results\n\n```\nbackground_output(task_id=\"[agent_1_id]\")\nbackground_output(task_id=\"[agent_2_id]\")\n...\n```\n\n**Mark phase-1 as completed after all results collected.**\n\n---\n\n";

package/dist/features/builtin-commands/templates/refactor-sections/plan-and-execution.d.ts

@@ -1 +1 @@
-export declare const REFACTOR_PLAN_AND_EXECUTION = "# PHASE 4: PLAN GENERATION (PLAN AGENT)\n\n**Mark phase-4 as in_progress.**\n\n## 4.1: Invoke Plan Agent\n\n```\nTask(\n  subagent_type=\"plan\",\n  prompt=\"Create a detailed refactoring plan:\n\n  ## Refactoring Goal\n  [User's original request]\n\n  ## Codemap (from Phase 2)\n  [Insert codemap here]\n\n  ## Test Coverage (from Phase 3)\n  [Insert verification plan here]\n\n  ## Constraints\n  - MUST follow existing patterns: [list]\n  - MUST NOT break: [critical paths]\n  - MUST run tests after each step\n\n  ## Requirements\n  1. Break down into atomic refactoring steps\n  2. Each step must be independently verifiable\n  3. Order steps by dependency (what must happen first)\n  4. Specify exact files and line ranges for each step\n  5. Include rollback strategy for each step\n  6. Define commit checkpoints\"\n)\n```\n\n## 4.2: Review and Validate Plan\n\nAfter receiving plan from Plan agent:\n\n1. **Verify completeness**: All identified files addressed?\n2. **Verify safety**: Each step reversible?\n3. **Verify order**: Dependencies respected?\n4. **Verify verification**: Test commands specified?\n\n## 4.3: Register Detailed Todos\n\nConvert Plan agent output into granular todos:\n\n```\nTodoWrite([\n  // Each step from the plan becomes a todo\n  {\"id\": \"refactor-1\", \"content\": \"Step 1: [description]\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"verify-1\", \"content\": \"Verify Step 1: run tests\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"refactor-2\", \"content\": \"Step 2: [description]\", \"status\": \"pending\", \"priority\": \"medium\"},\n  {\"id\": \"verify-2\", \"content\": \"Verify Step 2: run tests\", \"status\": \"pending\", \"priority\": \"medium\"},\n  // ... continue for all steps\n])\n```\n\n**Mark phase-4 as completed.**\n\n---\n\n# PHASE 5: EXECUTE REFACTORING (DETERMINISTIC EXECUTION)\n\n**Mark phase-5 as in_progress.**\n\n## 5.1: Execution Protocol\n\nFor EACH refactoring step:\n\n### Pre-Step\n1. Mark step todo as `in_progress`\n2. Read current file state\n3. Verify lsp_diagnostics is baseline\n\n### Execute Step\nUse appropriate tool:\n\n**For Symbol Renames:**\n```typescript\nlsp_prepare_rename(filePath, line, character)  // Validate rename is possible\nlsp_rename(filePath, line, character, newName)  // Execute rename\n```\n\n**For Pattern Transformations:**\n```typescript\n// Preview first\nast_grep_replace(pattern, rewrite, lang, dryRun=true)\n\n// If preview looks good, execute\nast_grep_replace(pattern, rewrite, lang, dryRun=false)\n```\n\n**For Structural Changes:**\n```typescript\n// Use Edit tool for precise changes\nedit(filePath, oldString, newString)\n```\n\n### Post-Step Verification (MANDATORY)\n\n```typescript\n// 1. Check diagnostics\nlsp_diagnostics(filePath)  // Must be clean or same as baseline\n\n// 2. Run tests\nbash(\"bun test\")  // Or appropriate test command\n\n// 3. Type check\nbash(\"tsc --noEmit\")  // Or appropriate type check\n```\n\n### Step Completion\n1. If verification passes \u2192 Mark step todo as `completed`\n2. If verification fails \u2192 **STOP AND FIX**\n\n## 5.2: Failure Recovery Protocol\n\nIf ANY verification fails:\n\n1. **STOP** immediately\n2. **REVERT** the failed change\n3. **DIAGNOSE** what went wrong\n4. **OPTIONS**:\n   - Fix the issue and retry\n   - Skip this step (if optional)\n   - Consult oracle agent for help\n   - Ask user for guidance\n\n**NEVER proceed to next step with broken tests.**\n\n## 5.3: Commit Checkpoints\n\nAfter each logical group of changes:\n\n```bash\ngit add [changed-files]\ngit commit -m \"refactor(scope): description\n\n[details of what was changed and why]\"\n```\n\n**Mark phase-5 as completed when all refactoring steps done.**\n\n---\n\n";
+export declare const REFACTOR_PLAN_AND_EXECUTION = "# PHASE 4: PLAN GENERATION (PLAN AGENT)\n\n**Mark phase-4 as in_progress.**\n\n## 4.1: Invoke Plan Agent\n\n```\nTask(\n  subagent_type=\"plan\",\n  prompt=\"Create a detailed refactoring plan:\n\n  ## Refactoring Goal\n  [User's original request]\n\n  ## Codemap (from Phase 2)\n  [Insert codemap here]\n\n  ## Test Coverage (from Phase 3)\n  [Insert verification plan here]\n\n  ## Constraints\n  - MUST follow existing patterns: [list]\n  - MUST NOT break: [critical paths]\n  - MUST run tests after each step\n\n  ## Requirements\n  1. Break down into atomic refactoring steps\n  2. Each step must be independently verifiable\n  3. Order steps by dependency (what must happen first)\n  4. Specify exact files and line ranges for each step\n  5. Include rollback strategy for each step\n  6. Define commit checkpoints\"\n)\n```\n\n## 4.2: Review and Validate Plan\n\nAfter receiving plan from Plan agent:\n\n1. **Verify completeness**: All identified files addressed?\n2. **Verify safety**: Each step reversible?\n3. **Verify order**: Dependencies respected?\n4. **Verify verification**: Test commands specified?\n\n## 4.3: Register Detailed Todos\n\nConvert Plan agent output into granular todos:\n\n```\nTodoWrite([\n  // Each step from the plan becomes a todo\n  {\"id\": \"refactor-1\", \"content\": \"Step 1: [description]\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"verify-1\", \"content\": \"Verify Step 1: run tests\", \"status\": \"pending\", \"priority\": \"high\"},\n  {\"id\": \"refactor-2\", \"content\": \"Step 2: [description]\", \"status\": \"pending\", \"priority\": \"medium\"},\n  {\"id\": \"verify-2\", \"content\": \"Verify Step 2: run tests\", \"status\": \"pending\", \"priority\": \"medium\"},\n  // ... continue for all steps\n])\n```\n\n**Mark phase-4 as completed.**\n\n---\n\n# PHASE 5: EXECUTE REFACTORING (DETERMINISTIC EXECUTION)\n\n**Mark phase-5 as in_progress.**\n\n## 5.1: Execution Protocol\n\nFor EACH refactoring step:\n\n### Pre-Step\n1. Mark step todo as `in_progress`\n2. Read current file state\n3. Verify lsp_diagnostics is baseline\n\n### Execute Step\nUse appropriate tool:\n\n**For Symbol Renames:**\n```typescript\nlsp_prepare_rename(filePath, line, character)  // Validate rename is possible\nlsp_rename(filePath, line, character, newName)  // Execute rename\n```\n\n**For Pattern Transformations:**\n```bash\n// Preview first\nsg --pattern '[pattern]' --rewrite '[rewrite]' --lang ts path/to/file.ts\n\n// If preview looks good, execute\npython3 scripts/ast_grep_helper.py replace '[pattern]' '[rewrite]' --lang ts path/to/file.ts --apply\n```\n\n**For Structural Changes:**\n```typescript\n// Use Edit tool for precise changes\nedit(filePath, oldString, newString)\n```\n\n### Post-Step Verification (MANDATORY)\n\n```typescript\n// 1. Check diagnostics\nlsp_diagnostics(filePath)  // Must be clean or same as baseline\n\n// 2. Run tests\nbash(\"bun test\")  // Or appropriate test command\n\n// 3. Type check\nbash(\"tsc --noEmit\")  // Or appropriate type check\n```\n\n### Step Completion\n1. If verification passes \u2192 Mark step todo as `completed`\n2. If verification fails \u2192 **STOP AND FIX**\n\n## 5.2: Failure Recovery Protocol\n\nIf ANY verification fails:\n\n1. **STOP** immediately\n2. **REVERT** the failed change\n3. **DIAGNOSE** what went wrong\n4. **OPTIONS**:\n   - Fix the issue and retry\n   - Skip this step (if optional)\n   - Consult oracle agent for help\n   - Ask user for guidance\n\n**NEVER proceed to next step with broken tests.**\n\n## 5.3: Commit Checkpoints\n\nAfter each logical group of changes:\n\n```bash\ngit add [changed-files]\ngit commit -m \"refactor(scope): description\n\n[details of what was changed and why]\"\n```\n\n**Mark phase-5 as completed when all refactoring steps done.**\n\n---\n\n";

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 ast_grep_replace with dryRun=true 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` 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";

package/dist/features/builtin-commands/templates/refactor-sections/verification-and-tooling.d.ts

@@ -1 +1 @@
-export declare const REFACTOR_VERIFICATION_AND_TOOLING = "# PHASE 6: FINAL VERIFICATION (REGRESSION CHECK)\n\n**Mark phase-6 as in_progress.**\n\n## 6.1: Full Test Suite\n\n```bash\n# Run complete test suite\nbun test  # or npm test, pytest, go test, etc.\n```\n\n## 6.2: Type Check\n\n```bash\n# Full type check\ntsc --noEmit  # or equivalent\n```\n\n## 6.3: Lint Check\n\n```bash\n# Run linter\neslint .  # or equivalent\n```\n\n## 6.4: Build Verification (if applicable)\n\n```bash\n# Ensure build still works\nbun run build  # or npm run build, etc.\n```\n\n## 6.5: Final Diagnostics\n\n```typescript\n// Check all changed files\nfor (file of changedFiles) {\n  lsp_diagnostics(file)  // Must all be clean\n}\n```\n\n## 6.6: Generate Summary\n\n```markdown\n## Refactoring Complete\n\n### What Changed\n- [List of changes made]\n\n### Files Modified\n- `path/to/file.ts` - [what changed]\n- `path/to/file2.ts` - [what changed]\n\n### Verification Results\n- Tests: PASSED (X/Y passing)\n- Type Check: CLEAN\n- Lint: CLEAN\n- Build: SUCCESS\n\n### No Regressions Detected\nAll existing tests pass. No new errors introduced.\n```\n\n**Mark phase-6 as completed.**\n\n---\n\n# CRITICAL RULES\n\n## NEVER DO\n- Skip lsp_diagnostics check after changes\n- Proceed with failing tests\n- Make changes without understanding impact\n- Use `as any`, `@ts-ignore`, `@ts-expect-error`\n- Delete tests to make them pass\n- Commit broken code\n- Refactor without understanding existing patterns\n\n## ALWAYS DO\n- Understand before changing\n- Preview before applying (ast_grep dryRun=true)\n- Verify after every change\n- Follow existing codebase patterns\n- Keep todos updated in real-time\n- Commit at logical checkpoints\n- Report issues immediately\n\n## ABORT CONDITIONS\nIf any of these occur, **STOP and consult user**:\n- Test coverage is zero for target code\n- Changes would break public API\n- Refactoring scope is unclear\n- 3 consecutive verification failures\n- User-defined constraints violated\n\n---\n\n# Tool Usage Philosophy\n\nYou already know these tools. Use them intelligently:\n\n## LSP Tools\nLeverage LSP tools for precision analysis. Key patterns:\n- **Understand before changing**: `LspGotoDefinition` to grasp context\n- **Impact analysis**: `LspFindReferences` to map all usages before modification\n- **Safe refactoring**: `lsp_prepare_rename` \u2192 `lsp_rename` for symbol renames\n- **Continuous verification**: `lsp_diagnostics` after every change\n\n## AST-Grep\nUse `ast_grep_search` and `ast_grep_replace` for structural transformations.\n**Critical**: Always `dryRun=true` first, review, then execute.\n\n## Agents\n- `explore`: Parallel codebase pattern discovery\n- `plan`: Detailed refactoring plan generation\n- `oracle`: Read-only consultation for complex architectural decisions and debugging\n- `librarian`: **Use proactively** when encountering deprecated methods or library migration tasks. Query official docs and OSS examples for modern replacements.\n\n## Deprecated Code & Library Migration\nWhen you encounter deprecated methods/APIs during refactoring:\n1. Fire `librarian` to find the recommended modern alternative\n2. **DO NOT auto-upgrade to latest version** unless user explicitly requests migration\n3. If user requests library migration, use `librarian` to fetch latest API docs before making changes\n\n---\n\n**Remember: Refactoring without tests is reckless. Refactoring without understanding is destructive. This command ensures you do neither.**\n\n<user-request>\n$ARGUMENTS\n</user-request>\n";
+export declare const REFACTOR_VERIFICATION_AND_TOOLING = "# PHASE 6: FINAL VERIFICATION (REGRESSION CHECK)\n\n**Mark phase-6 as in_progress.**\n\n## 6.1: Full Test Suite\n\n```bash\n# Run complete test suite\nbun test  # or npm test, pytest, go test, etc.\n```\n\n## 6.2: Type Check\n\n```bash\n# Full type check\ntsc --noEmit  # or equivalent\n```\n\n## 6.3: Lint Check\n\n```bash\n# Run linter\neslint .  # or equivalent\n```\n\n## 6.4: Build Verification (if applicable)\n\n```bash\n# Ensure build still works\nbun run build  # or npm run build, etc.\n```\n\n## 6.5: Final Diagnostics\n\n```typescript\n// Check all changed files\nfor (file of changedFiles) {\n  lsp_diagnostics(file)  // Must all be clean\n}\n```\n\n## 6.6: Generate Summary\n\n```markdown\n## Refactoring Complete\n\n### What Changed\n- [List of changes made]\n\n### Files Modified\n- `path/to/file.ts` - [what changed]\n- `path/to/file2.ts` - [what changed]\n\n### Verification Results\n- Tests: PASSED (X/Y passing)\n- Type Check: CLEAN\n- Lint: CLEAN\n- Build: SUCCESS\n\n### No Regressions Detected\nAll existing tests pass. No new errors introduced.\n```\n\n**Mark phase-6 as completed.**\n\n---\n\n# CRITICAL RULES\n\n## NEVER DO\n- Skip lsp_diagnostics check after changes\n- Proceed with failing tests\n- Make changes without understanding impact\n- Use `as any`, `@ts-ignore`, `@ts-expect-error`\n- Delete tests to make them pass\n- Commit broken code\n- Refactor without understanding existing patterns\n\n## ALWAYS DO\n- Understand before changing\n- Preview structural rewrites before applying them\n- Verify after every change\n- Follow existing codebase patterns\n- Keep todos updated in real-time\n- Commit at logical checkpoints\n- Report issues immediately\n\n## ABORT CONDITIONS\nIf any of these occur, **STOP and consult user**:\n- Test coverage is zero for target code\n- Changes would break public API\n- Refactoring scope is unclear\n- 3 consecutive verification failures\n- User-defined constraints violated\n\n---\n\n# Tool Usage Philosophy\n\nYou already know these tools. Use them intelligently:\n\n## LSP Tools\nLeverage LSP tools for precision analysis. Key patterns:\n- **Understand before changing**: `LspGotoDefinition` to grasp context\n- **Impact analysis**: `LspFindReferences` to map all usages before modification\n- **Safe refactoring**: `lsp_prepare_rename` \u2192 `lsp_rename` for symbol renames\n- **Continuous verification**: `lsp_diagnostics` after every change\n\n## AST-Grep\nUse the `ast-grep` skill helper or `sg` CLI for structural transformations.\n**Critical**: Always preview first, review, then execute.\n\n## Agents\n- `explore`: Parallel codebase pattern discovery\n- `plan`: Detailed refactoring plan generation\n- `oracle`: Read-only consultation for complex architectural decisions and debugging\n- `librarian`: **Use proactively** when encountering deprecated methods or library migration tasks. Query official docs and OSS examples for modern replacements.\n\n## Deprecated Code & Library Migration\nWhen you encounter deprecated methods/APIs during refactoring:\n1. Fire `librarian` to find the recommended modern alternative\n2. **DO NOT auto-upgrade to latest version** unless user explicitly requests migration\n3. If user requests library migration, use `librarian` to fetch latest API docs before making changes\n\n---\n\n**Remember: Refactoring without tests is reckless. Refactoring without understanding is destructive. This command ensures you do neither.**\n\n<user-request>\n$ARGUMENTS\n</user-request>\n";