projmux 0.15.2 → 0.16.0

package/docs/usage-tracking.md

@@ -1,22 +1,26 @@
 # Usage tracking
 
 `projmux agent usage` and `projmux internal status usage` report authoritative fixed-window
-utilisation for Claude/Codex and official named quota buckets for Antigravity.
+utilisation for Claude/Codex.
 `--model all`, the tmux
 HUD, and the statusbar usage popup use Settings > AI Settings > Enabled
-agents as the source of truth, so disabled Claude/Codex/Antigravity providers are
+agents as the source of truth, so disabled Claude/Codex providers are
 not refreshed or rendered on ambient/all surfaces. Explicit read-only
-requests such as `projmux agent usage --model claude`, `--model codex`, or
-`--model antigravity`
+requests such as `projmux agent usage --model claude` or `--model codex`
 still collect and render that provider even when it is disabled.
 
-Claude and Codex adapters read the upstream's own account view. Antigravity
-reads only the official managed statusline payload: `context_window` remains
-private conversation-local diagnostic metadata, while each valid `quota` map
-entry is a separate account row. Projmux preserves the upstream bucket ID and
-never guesses that an undocumented ID means `5h` or `weekly`. It does not infer
-quota, cadence, reset timestamps, or account limits from screen scraping,
-tokens, history, OAuth/cache files, or binary strings.
+Claude and Codex adapters read the upstream's own account view. projmux does
+not infer quota, cadence, reset timestamps, or account limits from screen
+scraping, tokens, history, OAuth/cache files, or binary strings.
+
+Antigravity has no usage adapter: Antigravity offers no official usage event,
+and projmux no longer reads its statusLine. `--model antigravity` is still
+accepted; it prints no rows and the `Antigravity usage unsupported` note (exit
+status 0), and an enabled Antigravity shows the same note on `--model all` and
+in the statusbar popup. Rows an older Antigravity adapter left in
+`snapshots.json` are never printed or projected, and leftover
+`usage/antigravity-*.json` sidecars and Antigravity statusbar visibility files
+are neither read nor deleted.
 
 Claude keeps the canonical aggregate `five_hour` and `seven_day` rows and also
 preserves structurally valid typed `limits[]` rows as named account quotas for
@@ -128,30 +132,6 @@ rollout fallback row records `source=rollout` plus the closed fallback reason.
 If neither lane produces rows, Manager preserves the previous source/value and
 adds a closed `stale_reason` to the last-known-good row.
 
-### Antigravity (`internal/core/usage/adapters/antigravity`)
-
-Local managed-statusline sidecars. No network or credential reads.
-
-- `context_window.used_percentage` and its conversation ID remain in the
-  private context sidecar for hook/notify diagnostics. They do not become
-  Usage snapshots. The legacy string percentage remains a writer fallback.
-- The official `quota` map is sorted by its exact bucket ID. Each valid bucket
-  becomes `window=quota`, `bucket=<upstream ID>` and renders as
-  `quota/<upstream ID>` on account-inspection surfaces.
-- Used percent is `100 * (1 - remaining_fraction)`. Non-finite or values
-  outside `[0,1]`, empty IDs, null/disabled entries, and negative relative
-  resets are ignored safely. Rejected and duplicate buckets are skipped
-  individually — the healthy buckets in the same map still become rows — and the
-  skip is reported by sorted row index only, never by bucket ID.
-- `reset_time` and optional `reset_in_seconds` are stored independently. An
-  absent relative reset differs from explicit zero; no value is derived from
-  the other.
-- Context and quota use independent private sidecars. A context-only payload
-  does not erase the last quota observation. An explicit empty/null quota map
-  records no buckets; the manager's existing rule still preserves prior model
-  rows when an adapter returns zero total rows. Context never participates in
-  that account-row replacement decision.
-
 ## Snapshot store
 
 ```
@@ -180,7 +160,7 @@ across machines (Dropbox, iCloud Drive).
 ### `projmux agent usage`
 
 ```
-projmux agent usage [--model codex|claude|antigravity|all] [--window 5h|weekly|context|quota|all]
+projmux agent usage [--model codex|claude|all] [--window 5h|weekly|context|quota|all]
               [--json] [--force|-f]
 ```
 
@@ -192,7 +172,6 @@ Enabled agents, filters by window, and renders the tab-aligned table:
 MODEL        WINDOW                 PCT  RESETS_AT                 RESET_IN  STALE  SOURCE      REASON
 codex        5h/codex · General     12%  2026-05-07T14:00:00+09:00 -         app-server
 claude       5h                     80%  2026-05-07T14:00:00+09:00 -
-antigravity  quota/gemini-weekly    6%   2026-07-06T16:50:32+09:00 560580s
 claude       quota/group-redacted · Model Redacted Alpha  38%  2031-02-03T15:05:06+09:00  -  *
 ```
 
@@ -210,11 +189,9 @@ claude is in backoff, try again in 30m (use --force to bypass)
 
 When no AI agents are enabled, all-model table output contains no
 provider rows and prints a short Settings hint. `--json` returns an
-empty array. Explicit `--model claude`, `--model codex` and
-`--model antigravity` bypass the enabled-agent filter for read-only
-inspection and collect/render only the requested adapter. Antigravity reports
-zero or more account `quota/<bucket-id>` rows. Legacy cached `window=context`
-rows are suppressed in text and JSON output. `--window quota` selects only
+empty array. Explicit `--model claude` and `--model codex` bypass the
+enabled-agent filter for read-only inspection and collect/render only the
+requested adapter. Legacy cached `window=context` rows are suppressed in text and JSON output. `--window quota` selects only
 account buckets; `--window weekly` never matches an opaque quota bucket named
 `weekly`. `--window context` remains an accepted compatibility filter and
 returns no Usage rows.
@@ -236,11 +213,10 @@ after collection, throttle/backoff, and cache load. If no AI
 agents are enabled, the status segment emits nothing.
 
 The HUD first derives an ambient projection separate from lossless account
-snapshots. The explicit HUD capability map admits Claude/Codex `5h` and
-`weekly`, while Antigravity's exact `quota/gemini-weekly` identity alone is
-projected as `weekly`
-without rewriting the cache. Context, `3p-weekly`, and unknown quota buckets
-do not participate in status width. Claude `limits[]` named/model rows are also
+snapshots. The explicit HUD capability map admits only Claude/Codex `5h` and
+`weekly`. Context, named quota buckets, and cached rows from providers without
+a capability (such as the removed Antigravity adapter) do not participate in
+status width. Claude `limits[]` named/model rows are also
 excluded; only its aggregate official `5h` and `weekly` rows reach the HUD.
 The Settings provider list consumes `aiprovider.UsageSupported()` order, but a
 window toggle exists only when this same projection seam declares it. A future
@@ -248,11 +224,26 @@ provider or an opaque bucket cannot manufacture a window row.
 For native Codex multi-bucket rows, the exact `codex` bucket wins the HUD
 projection, then the legacy empty bucket, then lexical bucket order. The HUD
 compact identity is derived from that same row: a healthy authoritative
-`app-server` row is simply `Codex`, a fresh rollout row is
-`Codex [fallback]`, and a retained last-known-good row is `Codex [stale]`.
-Blank, malformed, or future non-stale provenance also fails conservatively to
-the existing `[fallback]` identity rather than looking native or expanding the
-compact vocabulary. The exact raw source and closed fallback/stale reason stay
+`app-server` row is simply `Codex`, a retained last-known-good row is
+`Codex [stale]`, and a fallback row keeps the bare `Codex` text while the HUD
+paints its label with the dedicated `provenance` theme color. Blank, malformed,
+or future non-stale provenance also fails conservatively to that same fallback
+presentation rather than looking native or expanding the compact vocabulary.
+
+That label used to spend 11 cells on a ` [fallback]` tag. It now spends none in
+the HUD and one in the text tiers, which is what the user asked for:
+*"이거 간단한 로드맵 거리긴한대 codex[fallback] 하단 status 바대신 주황색의 Codex가나오는게어때"*
+and, once the color-rule options were laid out, *"B로 가자"* — a role color of its
+own rather than a reused threshold color, with `[stale]` left alone. That role
+color is the public `provenance` theme token (`colour208` in the fallback
+theme); see [theme-palette.md](theme-palette.md).
+
+Below the bar tiers the segment is colorless, so a fallback row spells
+`Codex^ 5h:17%` there, or `X^ 5h:17%` at the single-letter tier: one ASCII cell
+in place of the tag. A client that cannot paint color, or a theme that sets
+`provenance` to the ordinary label color, therefore shows no fallback signal in
+the HUD at all — the recovery path is the full surface below.
+The exact raw source and closed fallback/stale reason stay
 in `agent usage --model codex` table/JSON output and in
 `projmux diagnostics log --component usage`; compact labels never replace
 those fields.
@@ -329,7 +320,19 @@ When a collection fails, the failure is visible in three places:
 
    The row carries the provider and closed source/failure enums and nothing else:
    `collect-failed` (whole-adapter failure, `level=error`) or `rows-skipped`
-   (partial failure, `level=info`). Codex rollout fallback records
+   (partial failure, `level=info`). A whole Claude failure names its class in
+   place of `collect-failed`, also at `level=error`:
+   `credentials-unavailable` (no credentials path resolved, or the credentials
+   file is missing, unreadable, or unparseable), `credentials-token-empty`,
+   `auth-rejected` (a 401 the stored refresh token could not recover from: no
+   refresh token, a failed refresh round-trip, or another 401 for the refreshed
+   token), `rate-limited` (429), `http-status` (any other non-200 response),
+   `network-error` (the request could not be built or sent, or its body could
+   not be read), or `response-invalid` (a 200 body that did not parse). The
+   class comes from the adapter's typed error, never from its message text. A
+   failure without a class stays `collect-failed`, and so does every whole
+   Codex failure. Status codes, paths, upstream bodies, and
+   credentials never reach the row. Codex rollout fallback records
    `source=rollout` plus its closed fallback reason; retained data records
    `source=last-known-good` plus its closed stale reason. A healthy native
    collection writes no row at all. Identical `(provider, source, failure)`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projmux",
-  "version": "0.15.2",
+  "version": "0.16.0",
   "description": "tmux project session manager",
   "license": "MIT",
   "homepage": "https://github.com/crevissepartners/projmux#readme",
@@ -28,9 +28,9 @@
     "package:npm:pack": "scripts/package-npm.sh --pack"
   },
   "optionalDependencies": {
-    "@projmux/linux-x64": "0.15.2",
-    "@projmux/linux-arm64": "0.15.2",
-    "@projmux/darwin-x64": "0.15.2",
-    "@projmux/darwin-arm64": "0.15.2"
+    "@projmux/linux-x64": "0.16.0",
+    "@projmux/linux-arm64": "0.16.0",
+    "@projmux/darwin-x64": "0.16.0",
+    "@projmux/darwin-arm64": "0.16.0"
   }
 }