BUGFIX
Remote tasks no longer get killed for "looking idle" during startup
When running Claude in a headless session (a purely background mode with no visible interface), if it was busy running startup hooks (scripts that automatically trigger at specific times) right after launching, the system used to sometimes fail to report its progress. This silence caused remote servers to assume it was idling (idle-reaped) and ruthlessly terminate it. Progress now streams correctly, proving it is still hard at work. It's like a warehouse worker who used to get fired for "slacking" because they were working quietly in the back; now they call out their progress as they go, avoiding wrongful termination.