PeterChrz 9bf17dba6f Make label part of band identity; correct ASUS GPU attribution ... Labels now define distinct sessions — different power-cap configs (asus_210w, sapphire_210w, asus_uncapped) render as separate bands instead of merging into one. The label badge displays alongside quant/engine/config badges rather than replacing them. Scenario drilldown filters by label to prevent cross-band mixing. Data fix: runs 22-32 (asus_210w) and 43-46 (asus_uncapped) reassigned from Sapphire (gpu_id=11) to ASUS (gpu_id=12) — they were run on the ASUS card but imported with the Sapphire GPU identity.		2026-10-04 23:18:21 -04:00
..
Console/Commands	Make label part of band identity; correct ASUS GPU attribution	2026-10-04 23:18:21 -04:00
Http	Device flow: one-time plaintext token pickup (plain_token stash), poll throttle 120/min for 3s CLI rhythm	2026-09-19 21:06:20 -04:00
Livewire	Phase 3: results table home page, run detail with owner notes/visibility, my-runs page	2026-09-16 22:41:12 -04:00
Models	Severity-ordered psychbench sections, streamlined run metadata card with server config YAML	2026-09-20 23:32:43 -04:00
Providers	Phase 2: benchmark_runs + run_results schema, models with visibility scope and immutability guard, factories, tests	2026-09-16 22:34:43 -04:00
Support	v2.2: depthsweep suite (table, model, registry, run-detail branch), band column headers, GpuSeeder in DatabaseSeeder, device-flow + catalog + confirm-picker tests	2026-09-19 21:11:20 -04:00