Per-OS-User + Per-RSI-Account Session Pinning

[ntatschner]

Problem

On a shared machine (multi-user Windows install, family gaming PC), the tray can silently inherit a previously-paired session into a different OS user's context. The same problem exists when a user re-links a different RSI account — the tray may continue running under the old session-pinning without prompting for re-auth.

Approach

Bind every active session to the triple (OS user, StarStats account, RSI account). On any change to any of the three, force re-auth or surface a "session changed" prompt.

Prevents:

• account mix-ups on shared machines
• silent session inheritance after an RSI re-link
• one StarStats account capturing another's events when the tray is left running

Acceptance criteria

• Session pinning triple persisted in the OS keychain alongside the existing cookie
• Any element of the triple changing triggers a session_changed UI prompt
• Prompt offers: "re-authenticate" / "sign out" / "this is correct, continue"
• Audit-log entry on each session-pin transition
• Multi-user Windows test: switching OS users while tray is running surfaces the prompt
• RSI re-link test: linking a different RSI handle surfaces the prompt

Risks / Open questions

• OS user identifier portability — Windows SID vs Linux UID vs macOS uid differ; need a stable cross-platform key
• False-positive prompts after legitimate password rotations / RSI handle rename
• Keychain access pattern under fast OS-user switching on Windows (the secure store may briefly be unavailable)
• Backward-compat: existing devices have no triple stored — first run after upgrade needs a one-time prompt to set it

Original draft notes

Bind every active session to the triple (OS user, StarStats account, RSI account). On any change to any of the three, force re-auth or surface a "session changed" prompt. Prevents account mix-ups on shared machines and silent session inheritance after an RSI re-link.

---

Tracking

• Roadmap slug: per-os-user-per-rsi-account-session-pinning
• Public roadmap: https://starstats.app/roadmap/per-os-user-per-rsi-account-session-pinning
• 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 — security-critical; must validate across all channels before going live to avoid silent session bleed. Add channel/<name> labels when targeting firms up.