Patch / Channel Tagging on Log Entries

[ntatschner]

Problem

Parsed log entries today don't record which RSI channel (LIVE / PTU / EPTU / Tech-Preview) or build number they came from. Cross-patch analytics ("my K/D over the last three LIVE patches") and patch-filtered views are impossible.

Approach

Tag every parsed log entry with its SC channel (LIVE / PTU / EPTU / Tech-Preview) and build number at parse time. Web + tray expose a multi-select channel filter; flipping the filter rebuilds the view without a page reload.

Channel is read from the Game.log header / install path at session start (not per-line), so the tag is consistent within a session.

Acceptance criteria

• Every parsed event row carries sc_channel + sc_build columns
• Migration is additive only (NULL for existing rows, populated forward)
• Web + tray Logs view gains a multi-select channel filter
• Filter UI is keyboard-navigable and remembered per-session
• Reference catalog queries can join on sc_channel for patch-aware lookups
• Channel detection works for all four channel install paths

Risks / Open questions

• Install path detection on non-standard install locations (custom drives, portable installs)
• User runs multiple channels concurrently from the same StarStats install — channel must be re-read per-session, not cached
• Per spec, migrations are additive only AND byte-immutable post-deploy — channel-tagging migration must follow the same rule
• PTU/EPTU naming may change between waves; needs to be a stable enum at the StarStats layer

Original draft notes

Tag every parsed log entry with its SC channel (LIVE / PTU / EPTU / Tech-Preview) and build number. Web + tray expose a multi-select channel filter; flipping the filter rebuilds the view without a page reload. Channel is read from the Game.log header / install path at session start.

---

Tracking

• Roadmap slug: patch-channel-tagging-on-log-entries
• Public roadmap: https://starstats.app/roadmap/patch-channel-tagging-on-log-entries
• Project board: https://github.com/orgs/TheCodeSaiyan/projects/1
• eta_band: tbd (set on the Project board when scoping firms up)
• Channel targeting: likely live + beta + alpha — infrastructure; Optional Killed-By Correlation — Inferred K/D (Stats Only) #116 K/D and Game Running Status + Session Metrics (Anti-Cheat-Safe) #120 game-running both depend on patch context. Add channel/<name> labels when targeting firms up.