BPS v0.15.0 - the Hub goes live

The Control Center concepts are now a working service: agents push, the hub aggregates, the wall and the radar render live data.

Agent: fleet uplink (opt-in)
Create ~/.bps/hub.json with the hub URL, your org's token, and site identity — from then on every trace and speed test pushes a compact summary to the hub. Best-effort by design: a down hub never affects the client-side diagnosis. Off by default; requires client consent.

Hub: hub/hub_server.py (stdlib + SQLite, zero dependencies)

• / — the fleet wall, live: KPIs, severity-sorted client tiles, verdict-change feed, blame grouping, and correlated transit events (the same suspect degrading ≥ 2 clients at once)
• /map — the probe radar, live: every agent plotted on South Africa, storm cells where neighbouring probes degrade together, automatic classification (multi-ISP + one region = infrastructure/power · one ISP + many regions = provider core · shared transit suspect = upstream event), national internet-weather index
• Token provisioning CLI, staff-token gate on all views, seed_demo.py for demos, README with deploy steps

Verified end-to-end: a seeded 12-client fleet produced the Angola Cables correlation, a Polokwane infrastructure cell and an Openserve core event — and then a real agent traced google.com and appeared live on both the wall and the map.

EV-signed by BURIKA DATACENTRE SOLUTIONS (PTY) LTD.
SHA-256: 355989045BB33590A2C5A917D52433C2DF6959AFDDC24A71D0CEE81D04B00571