Changelog
Two streams: (1) Manual notes in data/changelog.json. (2) Session scans — Cursor cannot see your Pi directly, but after a session run php /var/www/html/tools/changelog_session_scan.php on the server; it records files saved since the last run into data/changelog_auto.json (shown with a “Session scan” tag). The first run only sets a baseline. The card below is the live home-page “Status” — same idea as recent saves, not a written log.
Live snapshot (home page logic)
Status: Polishing the Network Visualizer on ChrisCloud — OSI steps, speed controls, step history. as of 4/13/2026 4:16 PM CDT
Last successful backup: Mon, Apr 13, 2026, 2:30 AM
← Back to home
2026-04-08
Partylytics: HUD OCR is steadier + shows “Scanning…”
- The Mac HUD reader is better at the corner star/coin counters (handles common OCR mixups and noisy digits).
- Added a “Scanning…” indicator while the HUD script is running (spinner in the terminal, plus a small status on the Partylytics page when live data is flowing).
- Added an optional debug mode that saves the cropped + preprocessed HUD images so you can see what OCR is actually reading.
2026-04-07
Apr 7, 2026 9:30 PM CDT
Partylytics: easier live updates + nicer charts
- The companion script can watch a local JSON file and send updates to the Pi (so your Mac can drive the dashboard without extra plumbing).
- Demo data was adjusted so the “coins over time / stars over time” charts look more like a real session.
- Charts got quality-of-life controls: drag to zoom, double-click to reset, and a quick “delta” readout when you click two points on the same line.
- Verified the Pi ingest end-to-end; the rest of the Mac-side wiring is saved for later.
2026-04-07
Apr 7, 2026 6:00 PM CDT
Changelog tweaks + Partylytics refresh link
- Clarified that the changelog is edited by hand (it doesn’t auto-update like the home page Status card).
- You can add an optional time (“when”) for multiple posts in one day, and an optional “detail” section for longer notes.
- Moved the small refresh link from the home page to Partylytics (next to ChrisCloud Home).
Use "detail" for anything too long for bullets — stack traces, file lists, reasoning, or a session recap after a big batch of edits. ISO-ish "when" values sort entries; if omitted, the calendar date is used (noon Central).
Refreshing /changelog only reloads whatever is already in the JSON file.