Align fleet runner comment with settle and stall timers

Docs already split FLEET_REPORT_SETTLE_MS from FLEET_STALL_POLL_MS; the runner wiring comment still blamed quiet detection on the settle timer. Match the two-timer design so the next doc pass cannot re-poison from this call site.

Author: TheGreatAxios

src/tui/runner.ts

@@ -2210,8 +2210,9 @@ export async function runTUI(initialConfig: Config): Promise<number> {
 
   // The fleet reports itself. Store changes drive it, so a lane finishing or
   // failing is on screen the moment it happens rather than at the next turn
-  // boundary; the timer covers the one change that produces no event at all,
-  // a lane going quiet. `observeFleet` decides what is worth saying.
+  // boundary. The settle timer coalesces a parallel burst into one observation;
+  // the stall poll re-runs so a lane that goes quiet with no further store
+  // event is still announced once. `observeFleet` decides what is worth saying.
   let fleetWatch = createFleetWatch();
   const reportFleet = (): void => {
     const observation = observeFleet(fleetWatch, subAgentSessions.list(), Date.now());