v1.15.0

Restored: the loop command

scan-local -> enhance -> rescan-local, chained into one command with no manual step in between —
an opt-in single-shot convenience for a quick pass (e.g. a POC). The three-separate-commands path
stays the default recommendation, since it lets you review the enhance diff before re-scanning.

loop was removed in v1.14.0 over a theory that two Quick Tunnels opened back-to-back were
unreliable. That theory turned out to be wrong: the real cause was tunnel.js probing a
freshly-minted tunnel hostname before it was actually safe to. Fixed directly (gate the first probe
on cloudflared's own "precheck complete" signal) — two tunnels in one process are now no less
reliable than one, so loop came back.

Side effect of chasing that fix down: is-agentic's long-standing "could not fetch homepage" error
against subfolder-hosted sites (e.g. a GitHub Pages project site) is now confirmed to be a
scanner-side bug that breaks on any non-root path — not something siteready can fix, but no longer
a mystery either.

New: local-scan vs. deployed-URL score gap, documented and surfaced

scan-local/rescan-local/loop only run a platform's real edge runtime locally for Cloudflare
Pages and Vercel. Every other platform (Netlify, GitLab Pages, generic static-host fallback) gets a
plain static-file server, which can't execute that platform's edge functions — confirmed
concretely for Netlify, whose markdown-negotiation Edge Function fix can only be verified against a
real deploy. A local scan now prints a clear note when this applies, and the same note is written
into report.md/report.json (localScanNote) — instead of the local score just reading lower
with no explanation.

Fixed

• A latent bug in loop (present before its v1.14.0 removal too, not introduced here): it was
  missing the same Jekyll guard scan-local already had.
• Stale documentation describing the reverted Quick Tunnel min-gap guard as still-current behavior
  (docs/architecture.md, SKILL.md, CLI help text).

Full history: WORKLOG.md.