發布日期：2026-09-05
你在 usage 查詢用量時，若裝有 Antigravity，過去切到互動儀表板只會看到 No data 的空白分頁。
問題在於儀表板與 usage report 各自維護代理到載入器的對照表，先前只有報表納入 antigravity，即便報表指令能載入用量，偵測到安裝的儀表板分頁依然只渲染出 No data；終端機表格也缺少 Antigravity 的簡稱與顯示名稱，欄位標題只能留著原始小寫代理 ID。兩份對照表過去缺乏一致性檢查，最初的迴歸測試（防範舊功能被改壞的自動驗證）甚至直接寫死三款已知代理而未比對雙方清單，無法維持鍵值同步；現在測試已強制要求兩邊鍵值完全相等。
When checking usage with usage, if Antigravity was installed, switching to the interactive dashboard previously only showed a blank tab with No data.
The problem was that the dashboard and usage report each maintained separate agent-to-loader mapping tables. Previously, only the report included antigravity, so even though the report command could load usage, the dashboard tab for a detected installation still rendered No data. Terminal tables also lacked Antigravity's short and display names, leaving column headers stuck with the raw lowercase agent ID. The two mapping tables previously lacked consistency checks, and the initial regression tests (automated checks preventing existing features from breaking) even hard-coded three known agents instead of comparing both lists, failing to keep keys synchronized; tests now enforce exact key equality across both sides.
**Antigravity usage now appears in the interactive dashboard with consistent labels.** The dashboard and `usage report` maintain separate agent-to-loader maps, and only the report map included `antigravity`, so a detected Antigravity installation opened a dashboard tab that rendered `No data` even though the report command could load its usage. The terminal tables also lacked Antigravity's short and display names, leaving their headings as the raw lowercase agent ID. The maps had no parity check, and the first regression test hard-coded the three known agents instead of comparing the two maps, so it could not keep their keys synchronized; it now asserts exact key equality. Reported and fixed by @ClarenceKuo in #126.