feat: add secure Hypersnap HTTP failover

[ael-dev3]

Summary

• add a hardened HTTPS/JSON Hypersnap adapter for the Haatz public read node
• switch Hypersnap only at whole-source session boundaries with durable identity, cursor, and event-fingerprint continuity checks
• prefer the local gRPC node, use Haatz while it is unavailable, and automatically fail back after compatible recovery probes
• preserve derived-source labeling and incomplete-history warnings
• update doctor, Windows tooling, reconstruction, security, and operations documentation

Selection note

Hypersnap does not expose node age or historical uptime. Haatz is selected because hypersnap.org currently designates it as the public default and live validation found it synchronized; the code does not claim it is objectively the oldest node.

Safety

• exact HTTPS origin and peer/version pins
• no provider credentials or redirects
• bounded streamed JSON and strict protocol validation
• canonical shard/block time hydration across REST and gRPC
• persistent source enrollment and conflict fingerprints
• fail-closed handoff on identity, topology, cursor, or content mismatch
• Haatz remains derived, never verified Hyper

Validation

• pnpm lint
• pnpm typecheck
• pnpm test (164 core + 25 UI + 71 Worker)
• pnpm build
• pnpm test:e2e (8/8)
• pnpm security:check
• live doctor: Neynar Snapchain and Haatz Hypersnap protocol checks passed
• runtime smoke: Haatz active on 2/2 shards with advancing cursors and zero reconnects; local Hypersnap container remained running