fleetd #796: document bootstrap retry readiness bound

2026-10-06 18:26:01 +02:00
parent c88f01ecb8
commit 027d413ce9
1 changed files with 4 additions and 3 deletions
@@ -1466,7 +1466,7 @@ public record FleetConfig(
     *                     CALLING lead's own turn to end (its pane to report {@code IDLE} or
     *                     {@code DONE}) before ending that pane's process at all. See the
     *                     paragraph above.
-     * @param relaunchReadySeconds default 45 — bound on EACH of two separate waits that run after
+     * @param relaunchReadySeconds default 45 — bound on EACH of three separate waits that run after
     *                     the old lead's pane has been torn down and a fresh one launched: first,
     *                     for the fresh pane itself to reach a real turn boundary ({@code IDLE} or
     *                     {@code DONE}, never merely {@code BLOCKED}) — the safety gate, since
@@ -1479,8 +1479,9 @@ public record FleetConfig(
     *                     10s live), so a budget has to clear more than one scan interval to leave
     *                     any real margin for the CLI's own boot time; 20 was rejected for exactly
     *                     that reason — at a 10s scan interval it only buys two scans. 45 buys
-     *                     roughly four. Only a timeout on the FIRST wait (the pane never becomes
-     *                     ready) withholds {@code bootstrapText}.
+     *                     roughly four; third, to retry sending {@code bootstrapText} while herdr
+     *                     reports {@code agent_not_ready}. A timeout on the first wait or the third
+     *                     one withholds {@code bootstrapText}.
     * @param bootstrapText default a sentence naming the RESOLVED handover path — sent to the
     *                     fresh lead's pane once it reaches a real turn boundary after relaunch,
     *                     telling the fresh session where to read the handover and carry on. Left