fix(inference): scope accuracy notices to the specific affected runs

[adibarra]

Note

Low Risk
Display-only change to when accuracy warnings appear; behavior is covered by new unit tests and does not touch auth or data pipelines.

Overview
Known-config accuracy warnings no longer blanket every point on a hardware/precision combo; they apply only to chart points whose GitHub Actions run id is listed on the issue (or to all runs when affectedRuns is omitted).

known-issues gains optional affectedRuns, optional run_url on matchable points, runIdFromRunUrl (parses /runs/<id>, ignores /attempts), and shared pointMatchesIssue used by matchKnownConfigIssues and by GPUGraph / ScatterGraph when choosing which points get warning arrows. GB300 Dynamo TRT MTP (FP8) and MI355X MoRI SGLang MTP (FP4) entries are wired to their specific bad runs. Tests were expanded around run-scoped vs unscoped matching.

^{Reviewed by Cursor Bugbot for commit c081168. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	Jun 17, 2026 8:34pm