fix(autofire): reset miss counter when agent produces output during tool call

The escalation path (10 misses → drop notification) was firing prematurely
when the coordinator was mid-tool-call: no ❯ visible, but the agent was
actively working. The interval now tracks the previous tick's tail — if new
output arrived the miss count resets to zero. Escalation only triggers when
the tail has been completely static for 10+ seconds with no prompt visible.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: brooksc

TODOS.md

@@ -11,10 +11,9 @@
 
 ## Known edge cases — no fix yet
 
-### 7. Autofire expiry window — coordinator in long tool call during countdown
+### ~~7. Autofire expiry window — coordinator in long tool call during countdown~~ ✅ COMPLETE
 
-**What's wrong:** If the coordinator is mid-tool-call when autofire countdown fires, it finds no PTY prompt, misses 10 times, and escalates unnecessarily.
-**No fix yet** — depends on timing; low frequency in practice.
+Fixed: the interval now tracks the last-seen tail. If new output arrives since the previous tick the agent is actively working, so the miss counter resets to zero. Escalation only triggers when the tail has been completely static for 10+ consecutive seconds with no prompt visible.
 
 ### 8. Post-restart coordinator MCP config stale if coordinator process restarts
 

src/components/PromptInput.tsx

@@ -421,6 +421,7 @@ export function PromptInput(props: PromptInputProps) {
     lastStagedText = notification.text;
     autoFirePromptMissCount = 0;
     setText(notification.text);
+    let lastIntervalTail = '';
 
     // eslint-disable-next-line solid/reactivity -- intentional untracked reads in interval
     autoFireInterval = window.setInterval(() => {
@@ -437,12 +438,20 @@ export function PromptInput(props: PromptInputProps) {
         autoFireInterval = undefined;
         return;
       }
+      const currentTail = stripAnsi(untrack(() => getAgentOutputTail(props.agentId)));
+      // If the agent produced new output since the last tick it is actively working
+      // (e.g. mid-tool-call). Reset the miss counter so a long tool call doesn't
+      // accumulate misses and trigger the escalation path prematurely.
+      if (currentTail !== lastIntervalTail) {
+        autoFirePromptMissCount = 0;
+        lastIntervalTail = currentTail;
+      }
       const tick = processAutoFireTick({
         staged,
         now: Date.now(),
         controlledBy: untrack(() => store.tasks[props.taskId]?.controlledBy),
         questionActive: untrack(() => questionActive()),
-        tail: stripAnsi(untrack(() => getAgentOutputTail(props.agentId))),
+        tail: currentTail,
         currentMissCount: autoFirePromptMissCount,
       });
 
@@ -458,9 +467,7 @@ export function PromptInput(props: PromptInputProps) {
       }
       if (tick.outcome === 'no-prompt') {
         autoFirePromptMissCount = tick.newMissCount;
-        const tailSnippet = stripAnsi(untrack(() => getAgentOutputTail(props.agentId))).slice(
-          -PROMPT_MARKER_SCAN_CHARS,
-        );
+        const tailSnippet = currentTail.slice(-PROMPT_MARKER_SCAN_CHARS);
         if (autoFirePromptMissCount === 1 || autoFirePromptMissCount % 5 === 0) {
           logWarn('autofire', 'prompt not detected after autoFireAt', {
             taskId: props.taskId,