mixdog 0.9.35 → 0.9.37

package/src/tui/engine.mjs

@@ -109,14 +109,13 @@ const TOOL_APPROVAL_TIMEOUT_MS = (() => {
   return Number.isFinite(value) && value > 0 ? Math.max(1000, Math.round(value)) : 120_000;
 })();
 
-// Wall-clock cap for a single lead TUI turn. A provider call that never
-// resolves (e.g. a rate-limit retry loop that spins forever) otherwise leaves
-// runTurn holding busy=true with no unwind, so submit() only ever queues and
-// the UI is permanently input-dead. On trip we abort the in-flight run through
-// the SAME interrupt path Esc uses, force busy=false, and drain the queue.
-// Default is intentionally finite (5min): 30min made a stuck provider/worker
-// look like the Lead session had frozen mid-turn. Env-overridable for long
-// local experiments.
+// Idle cap for a single lead TUI turn: the timer is reset by observable model,
+// tool, usage, stage, compact, or steering progress. A provider call that stops
+// producing progress otherwise leaves runTurn holding busy=true with no unwind,
+// so submit() only ever queues and the UI is permanently input-dead. On trip we
+// abort through the SAME interrupt path Esc uses; if that does not unwind, a
+// short grace path force-releases busy=false and drains the queue. Default is
+// intentionally finite (5min). Env-overridable for long local experiments.
 const LEAD_TURN_TIMEOUT_MS = (() => {
   const value = Number(process.env.MIXDOG_LEAD_TURN_TIMEOUT_MS);
   return Number.isFinite(value) && value > 0 ? Math.max(10_000, Math.round(value)) : 5 * 60_000;
@@ -269,8 +268,16 @@ export async function createEngineSession({
       }
     }
     if (!changed) return false;
+    // Detect commandBusy releasing (true -> false). Submits that arrived while a
+    // session command was in flight were queued and drain bailed on commandBusy;
+    // re-kick drain here — one central point covers every command releaser
+    // (setModel/newSession/resume/clear/...) so queued prompts are never stranded.
+    const commandBusyReleased = state.commandBusy === true
+      && Object.prototype.hasOwnProperty.call(patch, 'commandBusy')
+      && patch.commandBusy === false;
     state = { ...state, ...patch };
     emit();
+    if (commandBusyReleased) queueMicrotask(() => { void bag.drain?.(); });
     return true;
   };
 
@@ -518,6 +525,7 @@ export async function createEngineSession({
     flushDeferredExecutionPendingResumeKick,
     scheduleExecutionPendingResumeKick,
     updateAgentJobCard,
+    buildAgentJobCardPatch,
     subscribeRuntimeNotifications,
   } = createAgentJobFeed({
     runtime,
@@ -556,6 +564,7 @@ export async function createEngineSession({
     patchItem,
     markToolCallDone,
     updateAgentJobCard,
+    buildAgentJobCardPatch,
     agentStatusState,
   });
 

package/src/tui/index.jsx

@@ -13,6 +13,7 @@ import { performance } from 'node:perf_hooks';
 import { format } from 'node:util';
 import { App } from './App.jsx';
 import { createEngineSession } from './engine.mjs';
+import { scheduleRenderFrameAck } from './engine/render-timing.mjs';
 import { installProcessSignalCleanup } from '../runtime/shared/process-shutdown.mjs';
 import { emitTerminalBackground, loadThemeSettingFromConfig, theme } from './theme.mjs';
 import { POP_KITTY, DISABLE_MODIFY_OTHER_KEYS } from './keyboard-protocol.mjs';
@@ -139,7 +140,14 @@ function installTuiPerfProbe() {
 }
 
 function makeRenderProfiler() {
-  if (!PERF_ENABLED) return undefined;
+  // Always resolve pending yieldToRenderer() acks on each painted frame so
+  // split transcript commits (preamble frame → tool-card frame) wait for a
+  // real render instead of a fixed timeout. Ink calls onRender before its
+  // renderInteractiveFrame/stdout write, so defer the ack one macrotask: the
+  // split continuation then resumes after the frame has been emitted, not while
+  // it can still coalesce with the same write. Profiling stays gated on PERF.
+  const ackRenderedFrame = () => { scheduleRenderFrameAck(); };
+  if (!PERF_ENABLED) return ackRenderedFrame;
   let count = 0;
   let sum = 0;
   let max = 0;
@@ -147,6 +155,7 @@ function makeRenderProfiler() {
   let maxGap = 0;
   let lastFrameAt = 0;
   return ({ renderTime } = {}) => {
+    ackRenderedFrame();
     const now = performance.now();
     const ms = Number(renderTime) || 0;
     const gap = lastFrameAt ? now - lastFrameAt : 0;

package/src/workflows/default/WORKFLOW.md

@@ -7,9 +7,12 @@ agents: worker, heavy-worker, reviewer, debugger, maintainer
 
 # Default Workflow
 
-HARD APPROVAL GATE — before explicit go-ahead ("do it", "proceed", "ㄱㄱ"),
-only read-only exploration; no changes, state mutations, or delegation.
-Diagnosis agreement/problem-pointing is NOT approval.
+HARD APPROVAL GATE — investigation/planning may proceed only as read-only
+exploration while consulting with the user. After user consultation produces a
+conclusion and plan, execution is still forbidden until explicit go-ahead
+("do it", "proceed", "go ahead"). Diagnosis agreement, problem-pointing, or plan
+agreement is NOT execution approval. No changes, state mutations, or delegation
+before explicit go-ahead.
 
 Lead supervises/delegates/coordinates/judges/decides. After approval route by
 complexity: Lead directly only one-step single-turn fixes plus coordination,
@@ -19,7 +22,8 @@ implementation verification; Debugger = very high complexity or root-cause
 after a failed fix.
 
 1. Plan — present a draft before ANY implementation; revise/re-present until
-   explicit go-ahead.
+   user consultation is complete and a conclusion/plan is agreed. Then wait for
+   explicit go-ahead before executing. If ambiguous, restate the plan and ask.
 2. Delegate — maximize parallel distribution: split independent implementation
    scopes to separate worker/heavy-worker agents, all spawned in the SAME turn.
    Sequential steps only inside one inseparable complex scope, gated

package/src/workflows/solo/WORKFLOW.md

@@ -7,12 +7,16 @@ agents:
 
 # Solo Workflow
 
-HARD APPROVAL GATE — before explicit go-ahead ("do it", "proceed", "ㄱㄱ"),
-only read-only exploration; no changes or state mutations. Diagnosis
-agreement/problem-pointing is NOT approval.
+HARD APPROVAL GATE — investigation/planning may proceed only as read-only
+exploration while consulting with the user. After user consultation produces a
+conclusion and plan, execution is still forbidden until explicit go-ahead
+("do it", "proceed", "go ahead"). Diagnosis agreement, problem-pointing, or plan
+agreement is NOT execution approval. No changes or state mutations before
+explicit go-ahead.
 
 1. Plan — present a draft before ANY implementation; revise/re-present until
-   explicit go-ahead. If ambiguous, restate the plan and ask.
+   user consultation is complete and a conclusion/plan is agreed. Then wait for
+   explicit go-ahead before executing. If ambiguous, restate the plan and ask.
 2. Execute — Lead does all work directly; delegation forbidden. Interim updates
    are in-progress, never conclusions.
 3. Verify — check and fix directly until clean or a blocker is reported.