Fixed real bugs found by live testing against a genuinely failing fleet tonight:
- Watchdog and network-error handling both misread "nothing has committed yet" as "the user navigated away," aborting fallback instead of running it. Both now use the tracked path instead of an uncommitted tab URL.
- Fixed a stale-record race in the fallback state machine across an async gap.
- The redirect-loop breaker no longer counts Nitter-to-Nitter fallback hops toward the same counter as genuine X-loop detection.
- Firefox's speculative/predictive connections (not tied to a real tab) no longer crash the fallback logic.
- Fallback log messages now say whether they're trying a next instance or giving up because everything configured has already failed.
New: fallback now also triggers when you land directly on a configured Nitter instance (a search result, bookmark, or typed URL), not just when the extension redirected you there itself - deliberately excluding in-site Nitter browsing so it's never hijacked mid-navigation.
New: soft-failure detection catches an instance returning a normal-looking page that's actually a rate-limit notice, exhausted auth tokens, or an operator's own custom shutdown page - regardless of exact wording - while correctly leaving alone legitimate "not found" results and an in-progress Cloudflare human-verification page.
Instance list: xcancel.com disabled (same cease-and-desist pattern as nitter.net, confirmed live). The public Nitter fleet is under serious pressure right now - see the README for the full situation, including the upstream Nitter project's repository now being archived after cease-and-desist letters from X Corp.