bridge-server.ts ~259: upstream sf8193#126 conditioned the flap-counter wipe on !mainHadOtherIncumbent, enabling the breaker — but the co-located comment still documents the unconditional wipe as deliberate, with the explicit warning that on a live 5s flap every reconnect reads hasOtherIncumbent=true, so the counter accumulates and the guard refuses main's own reconnects in ~50s with recurring 10s cooldowns (control-channel lockout). If the byte ever logs 'duplicate main bridge flapping — holding incumbent' on a single-process flap, revert to the unconditional wipe (one line).
bridge-server.ts ~259: upstream sf8193#126 conditioned the flap-counter wipe on !mainHadOtherIncumbent, enabling the breaker — but the co-located comment still documents the unconditional wipe as deliberate, with the explicit warning that on a live 5s flap every reconnect reads hasOtherIncumbent=true, so the counter accumulates and the guard refuses main's own reconnects in ~50s with recurring 10s cooldowns (control-channel lockout). If the byte ever logs 'duplicate main bridge flapping — holding incumbent' on a single-process flap, revert to the unconditional wipe (one line).