v1.14.0

Quick Tunnel reliability + loop command removed

Tunnel reliability fix: traced Cloudflare Quick Tunnel's DNS-propagation flap to spacing
between tunnel creations, not per-attempt delay. src/lib/tunnel.js now refuses to open a new
tunnel under a 2-minute gap since the last one (persisted across CLI invocations), with a clear
error naming how long to wait -- an evidence-based known-bad-zone filter, not a claim that 2
minutes is proven sufficient. Reachability-flap failures no longer retry back-to-back with no gap.
Added a rolling tunnel-count warning as usage nears the observed (undocumented) ~20/hour creation
rate limit.

Removed the loop command. Its whole design -- chaining baseline-scan -> enhance -> re-scan ->
diff-report into one automatic shot -- was exactly the back-to-back-tunnel pattern just proven
unreliable for hosted scanners (is-agentic/ora). No deprecation, since there are no real users
yet. New rescan-local command (scan-local's rescan counterpart) means the reliable replacement
workflow now exists: scan-local -> enhance -> rescan-local, run as three separate commands so
a real gap (e.g. reviewing the report) naturally falls between the two tunnel-needing steps.

Changed

• src/lib/tunnel.js: persisted min-gap guard, reachability-flap-aware retry loop, rate-limit
  proximity warning.
• src/cli.js: new rescan-local command; loop command removed.
• src/loop.js: runLoop removed (kept runScanLocal and its supporting helpers).
• scripts/verify-loop.js: rewritten to compose runScanLocal + enhance + buildDiffReport
  directly instead of calling the removed runLoop.
• README.md, docs/, SKILL.md, AGENTS.md, CONTRIBUTING.md: every loop reference replaced with the
  scan-local / enhance / rescan-local sequence.

Verified: npm run verify-loop green across all three reference fixtures, scripts/check-syntax.js clean.