steam-backlog-enforcer/web/src/budgetSeries.ts
Krzysztof kuhy Rudnicki 1faf211767 Show which games make up the gaming budget, and bill osu!lazer
The budget tab answered "how much did I play" but not "what did I play":
playtime_state.json and playtime_history.json each stored one aggregate
seconds figure per gaming day, so the 14-day chart was a row of featureless
bars. Separately, qualifying_pids had exactly two sources — the SteamAppId
env var and a hardcoded 16-launcher frozenset — so osu!lazer, which sets no
SteamAppId and matches no launcher name, was never billed at all.

qualifying_pids now returns pid -> attribution key instead of a bare pid set.
The app id was already in hand and thrown away on its first line; it now
survives into PlaytimeState.per_game, alongside a user-editable
counted_processes list in config.json seeded with osu!lazer.

Two things the parts/whole relationship forces:

  - per_game only ever sums to AT MOST seconds, never equals it. backdate
    refunds the idle grace on every engaged-to-paused edge, and
    _state_or_recover synthesises a full budget with no breakdown. The
    refund is debited from last_credited_key, and the remainder is rendered
    as "Unattributed" rather than stored — one path then covers legacy days,
    focus-probe failures and drift alike.

  - counted_processes is kept apart from LAUNCHER_PROCESS_NAMES. That
    frozenset is also the total-block kill list, and it routes through
    kill_and_uninstall_launchers, which pacman -R's the owning package.
    Counted entries are killed on total block, never uninstalled.

Both storage formats stay at schema 1: load_state already filters to
dataclass fields, so a record without per_game migrates for free, and the
history reader has to accept both a bare float and an object regardless, so
a version bump would distinguish nothing.

Chart segments use the shared design system's categorical ramp (--cat-1..6),
capped at six games plus "Other" because a seventh distinguishable hue does
not exist under simulated CVD. The red over-budget fill is gone: colour now
encodes which game, and the dashed budget line alone says over or under.

Snapshot persistence moves to _snapshot.py to keep config.py under the
250-line cap. Three modules bound config paths at import time, which
bypasses the conftest redirect — they now reach them through the module.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MKFzwzwRU1JD7SFLHtQBsz
2026-08-29 18:32:03 +02:00

30 lines
1.2 KiB
TypeScript

/**
* Colour assignment for the stacked budget chart.
*
* Kept out of the component because it is the one part with branches worth
* testing directly, and because the rule it encodes is not local: `--cat-1..6`
* come from the shared design system's categorical ramp, chosen under a
* pairwise CIE dE >= 20 constraint including simulated colour-vision
* deficiency. Six is the whole ramp -- a seventh distinguishable hue does not
* exist in that band, which is why the backend folds the tail into `other`.
*/
/** Games with no attribution, and the folded tail, sit outside the ramp. */
export const UNATTRIBUTED_KEY = 'unattributed'
export const OTHER_KEY = 'other'
/** Size of the categorical ramp; the backend caps series to match. */
export const SERIES_COLORS = 6
/**
* Return the CSS class for a legend entry at `index`.
*
* The two sentinels are deliberately neutral: they are absences of
* information, and giving them a ramp hue would read as "another game".
*/
export function seriesClass(key: string, index: number): string {
if (key === UNATTRIBUTED_KEY) return 'seg unattributed'
if (key === OTHER_KEY) return 'seg other'
return `seg cat-${(index % SERIES_COLORS) + 1}`
}