HeadlessTracker

Recovers automatically from a transient network blip instead of failing the account.

Fixed

• A transient network error is now retried once before failing. A connector that hit a momentary network failure (a dropped connection, a DNS hiccup, a connection refused) failed that account immediately, surfacing an error for what a single retry would have cleared. The orchestrator now retries once (after a short, abortable backoff) on a network_error -- the one error kind returned uniformly and only when fetch itself throws at the network layer. It deliberately does not retry upstream_error (mixes transient 5xx with non-transient 4xx and upstream logical errors), rate_limited (429s already back off in the price layer), auth_failed, or schema_mismatch. The retry is bounded by the v1.0.10 request deadline, so it can never push a call past the timeout, and it still falls back to stale cache if both attempts fail.

349 tests green.

Not financial advice -- data aggregation tool only.