Tab progress indicator stops permanently in one long-running session (Windows Terminal)

Environment

• Claude Code v2.1.168 (native Windows install, ~/.local/bin/claude.exe)
• Windows 11 Home (26200)
• Windows PowerShell 5.1, running inside Windows Terminal

Summary

With four Claude Code sessions open as tabs in one Windows Terminal window, one long-running claude --resume session never shows the tab progress indicator again, while the other three show it normally (including while paused at a permission prompt). It stays off for the entire lifetime of that process; restarting the session fixes it.

Investigation

The progress emitter is gated by AEH():

1. config progressReporting (explicit override)
2. process.stdout.isTTY
3. process.env.WT_SESSION

The emitter then SETs progress during an operation and CLEARs it when idle (via the iTerm2/terminal abstraction T2(lw.ITERM2, akH.PROGRESS, ...)).

I verified every gating input is identical across the four sessions:

• Same binary / version 2.1.168
• All four are powershell.exe children of the same WindowsTerminal.exe PID
• WT_SESSION present in all four processes (read directly from each process's environment block)
• progressReporting / progressBarEnabled set nowhere (global + 11 project .claude/settings.json + local)
• All four are TTYs

So AEH() returns true identically for all four. Despite that, the affected session never emits SET again — it appears the progress UI component emitted CLEAR and then stopped re-emitting for the rest of the process lifetime (suspected unmount/throw in the long-lived --resume session).

Repro (non-deterministic)

Run several claude --resume sessions as Windows Terminal tabs; after extended use, one session's progress indicator goes dark and never returns.

Expected

Progress indicator resumes for active operations.

Actual

Indicator never appears again for that session until it is exited and restarted.