projmux 0.15.2 → 0.15.3

package/docs/theme-palette.md

@@ -54,6 +54,7 @@ onto these stable names:
 | `action_required` | AI needs-input/approval badge color | AI action-required badge (independent of `critical`) |
 | `pane_active_bg` | active-pane background tint | active-pane window-active-style tint (tmux pane chrome) |
 | `focus` | active-pane border color | active-pane border (tmux pane chrome) |
+| `provenance` | fallback-data-source label color | compact usage label for a row served by a fallback source (never a usage threshold color) |
 
 `text_primary` and `chrome_foreground` split the old broad foreground behavior:
 changing primary content text no longer repaints frame/title/search/border/status
@@ -71,6 +72,17 @@ failure, destructive, over-limit, or risk states. `pane_active_bg` and `focus`
 are also public keys driving the active-pane tint and border (tmux-only pane
 chrome, with no ANSI/native role).
 
+`provenance` colors a compact usage label whose numbers came from a fallback
+data source instead of the provider's authoritative one (today: a Codex row
+outside a healthy app-server). It is deliberately neither `warning` nor
+`critical` — those mean usage thresholds — nor the `accent.ai` label color a
+healthy row uses, because it is the only signal that row carries. Every built-in
+preset defines it as an orange (hue 15-45°) whose nearest tmux color differs
+from that preset's five state colors and from `colour121`; the fallback theme
+uses `colour208`, and an explicit light `status_background` darkens that literal
+the same way it darkens the other statusbar text roles. It is a tmux-only role
+(`usage.provenance_fg`) with no ANSI/native counterpart.
+
 Renderer-only role names such as `accent.ai`, `state.progress`, `git.branch`,
 and trust colors remain in `internal/theme/palette.go` until Phase 2+ maps each
 surface to the resolver tokens. The key product contract for this phase is that
@@ -200,6 +212,7 @@ light experience with `daylight` also requires a light terminal theme.
 | `action_required` | `#d97706` | `colour172` |
 | `pane_active_bg` | `#e8e4dc` | `colour254` |
 | `focus` | `#2563eb` | `colour26` |
+| `provenance` | `#944400` | `colour94` |
 
 ## Fallback Inventory
 
@@ -221,6 +234,7 @@ Accents and state:
 | `accent.action` | `141;205;142`, strong `122;199;173` | `colour29` bg / `colour230` fg |
 | `accent.attention` | notify HUD background/project family | `colour53`, project `colour90` |
 | `accent.ai` | notify agent `colour37` family | `colour37` bg / `colour121` fg |
+| `usage.provenance_fg` | not emitted on native surfaces | `colour208` (public `provenance` token) |
 | `state.progress` | `255;204;102`; switch attention/busy dot, pane-border in-progress badge, and pending notify title/bell/badge `colour220` | `colour220` |
 | `state.action_required` | AI approval/input-required status badge amber-orange; currently aliases the established warning token | `colour214` |
 | `state.warning` | usage/status popup warning ANSI 256 wrapper; non-AI warning chrome | `colour214` |

package/docs/usage-tracking.md

@@ -248,11 +248,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 +344,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 or Antigravity 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.15.3",
   "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.15.3",
+    "@projmux/linux-arm64": "0.15.3",
+    "@projmux/darwin-x64": "0.15.3",
+    "@projmux/darwin-arm64": "0.15.3"
   }
 }