From 0545659c1b88834a24f4da84ad007d8a6db7d0b5 Mon Sep 17 00:00:00 2001
From: FuelBoard Contributor <fuelboard@localhost>
Date: Sat, 15 Aug 2026 08:43:59 +0100
Subject: [PATCH] =?UTF-8?q?Backlog:=20P0=20GitHub=20mirror=20=E2=80=94=20c?=
 =?UTF-8?q?apture=20telemetry=20implications=20(widget=20beacon=20survives?=
 =?UTF-8?q?,=20opportunistic=20app=20beacon,=20/stats=20canary=20+=20fallb?=
 =?UTF-8?q?ack-outage=20signal)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 BACKLOG.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/BACKLOG.md b/BACKLOG.md
index 57bf427..3bc0e7d 100644
--- a/BACKLOG.md
+++ b/BACKLOG.md
@@ -21,7 +21,13 @@ Status: TODO / IN PROGRESS / DONE / BLOCKED.
   fetches `raw.githubusercontent.com/aptonline/fuelboard-data/main/latest.json`,
   then only the missing day files for starred (station, fuel) pairs (deterministic
   URLs — 404 = no data that day, leave a graph gap, never error). LAN relay stays
-  the fallback source. Setup: create the PUBLIC repo `aptonline/fuelboard-data`
+  the fallback source. Telemetry implication: raw GitHub fetches are invisible to
+  repo analytics (page views/clones only) — keep the widget-diag beacon firing
+  regardless of data source (build/stale-build checks survive) and add an
+  opportunistic fire-and-forget X-Client app beacon on fetch (LAN = attribution +
+  cadence; off-LAN skip is itself a reachability datum). `/stats` keeps the
+  intrusion canary and gains a new signal: app-hit spikes = GitHub path failing →
+  fallback active. Setup: create the PUBLIC repo `aptonline/fuelboard-data`
   (gh installed); GitHub PAT (aptonline) lives in relay `.env` only — never in the
   repo or IPA. App Review: public repo required (reviewer fetches the data
   themselves); HTTPS/ATS fine; plain JSON is not "remote code" (2.5.2-safe); bundle