setup-cloudflare-tunnellisted

# Set up a Cloudflare quick-tunnel for the streamer The streamer binds to `127.0.0.1:8766` and isn't reachable from the network. To pair the mobile app from outside your LAN, you need a tunnel forwarding HTTPS traffic to that local port. A Cloudflare quick-tunnel is the fastest start — no account, no domain, ~30 seconds — and that's what this skill handles. Graduating to a persistent named tunnel (with optional Cloudflare Access) is a separate step the user can opt into at the end. **Authoritative references** — read these before going beyond the happy path: - [`docs/guides/remote-access/README.md`](../../../docs/guides/remote-access/README.md) — concept hub, provider comparison, security baseline. - [`docs/guides/remote-access/cloudflare.md`](../../../docs/guides/remote-access/cloudflare.md) — full Cloudflare guide (quick-tunnel + named tunnel + Access). Don't paraphrase from memory; quote or link. ## Step 1 — Make sure the streamer is actually running ```sh curl -s http://127.0.0.1:8766/healthz ``` Should print `{"ok":true,...}` with a version. If it doesn't, fix that first — the tunnel will be 502-ing if there's nothing on 8766. Send the user to `local-deploy` skill or `scripts/deploy.sh` to bring the streamer up. ## Step 2 — Pick the runner Prefer the Go TUI when `go` is on `PATH` — it renders progress more clearly. Otherwise run the shell script directly. Both produce identical results. ```sh # Detection command -v go >/dev/null 2>&1 && echo "go available" || ech