Description
Zone overviews usually show visits, page views, threats and uniques, and a month-to-date data transfer figure with a linear end-of-month projection is a cheap single account-level query that supports billing alerts. The 1-minute rollup groups that carry some of these are plan-gated, so prefer adaptive equivalents and record per-plan availability.
Acceptance Criteria
- #1 Visits and threat counts are exported where an adaptive or rollup dataset provides them on the zone plan, with the plan dependency documented
- #2 Account edge data transfer month-to-date and a linear projection are exported as gauges, eyeball-only
- #3 A new dataset or endpoint has a live-verified entry in doc-0003 and an API drift canary probe
- #4 Every new signal and attribute is declared in internal/semconv, listed in docs/signals.md, and has a panel in grafana/build_dashboard.py
Definition of Done
- #1 just check (fmt-check, lint, vet, test, tidy-check, build, vuln)
- #2 just ci before a change that touches the Dockerfile, goreleaser or the image (adds snapshot + image)
- #3 Every new signal or attribute name declared in internal/semconv and listed in docs/signals.md
Implementation Notes
A9v2 shared API contract/metadata/config seam landed at 9705290 after exact review, full gate, live integrated canary and ordinary CI; doc-0003 section 15 records verified visits, threats and account transfer selections and constraints. Local candidate 731ab6a passed real Register/HTTP red-then-green proof, full gate and CodeRabbit zero findings across six paths; fresh root independent review is active. AC1/2 remain unchecked until review and landing. Dashboard/live AC4 is unshipped beyond the final release boundary.
Fresh independent review rejected local candidate 731ab6a: visits used the ordinary API query boundary, which normalizes a null dataset to an empty array and could emit zero visits and advance the checkpoint. Root commissioned RR1 within owned HTTP files to use the existing strict raw batch boundary when visits is selected, with registered real-HTTP null-versus-empty/no-emission/no-checkpoint proof before and after the repair. The original passing tests covered null row fields, not null datasets. No shared cfapi semantics change or deployed feature claim is authorized.
RR2 candidate 6145796 received fresh independent PASS after strict raw-dataset and uint64-visits validation, plus registered Scheduler/HTTP red-then-green fractional/null controls. Root integration 69e47a7 passed exact-SHA full gate and both privacy scans and was pushed. Complete UTC threats windows, source-policy visits, contiguous account transfer partitions and exact month projection are locally verified. Current exact-SHA CI watcher remains pending; source AC1/2 are locally proven and landed. AC4 dashboard/live stays unshipped; no fourth release or deployment is authorized.
Loop16 RECON-M1 checked source criteria 4 against landed tests at ced4edfbfb66f1b9ee45037bdb425b69820a8ebe. Evidence: codex/evidence-loop16/RECON-return.txt. No new live or browser observation is claimed.
Final Summary
Loop16 reconciled all acceptance criteria on the landed source and cited test evidence.