projmux 0.15.3 → 0.16.0

package/docs/statusbar.md

@@ -29,17 +29,16 @@ row 1  [#S]  #{pane_current_path}  <git>  CPU 12%  MEM 41%   %H:%M
   state surface.
   Settings > Appearance > Status Bar controls `Notifications HUD` and `Agent
   Usage HUD` independently. Agent Usage HUD is a View whose `Visible` parent
-  contains Claude/Codex/Antigravity provider Views; each provider has its own
-  `Visible` plus explicit supported windows (Claude/Codex: `5h`, `Weekly`;
-  Antigravity: `Weekly`). Every leaf defaults on except Codex `5h`, which
+  contains Claude/Codex provider Views; each provider has its own
+  `Visible` plus explicit supported windows (`5h`, `Weekly`). Antigravity has
+  no usage source and no row. Every leaf defaults on except Codex `5h`, which
   defaults off; saving it as on explicitly restores that window. Parent off
   preserves saved children, and returning it on restores them. When only one HUD is visible, its
   sole range receives the full `#{client_width}` budget and the absent range and
   alignment are not emitted. When both are hidden, tmux collapses to one line
   with `status on`,
-  moves the native Window row to `status-format[0]`, unsets stale higher rows,
-  and keeps the app's quiet Session State autosave job on that surviving row;
-  there is no empty HUD row. These toggles hide presentation only and do not
+  moves the native Window row to `status-format[0]`, and unsets stale higher
+  rows; there is no empty HUD row. These toggles hide presentation only and do not
   mutate the Notification queue or usage collection/cache/API state.
   Provider/window visibility also changes only the ambient status projection;
   the cached popup and explicit `agent usage` table/JSON stay lossless. If every
@@ -304,11 +303,11 @@ as a secondary bar and cannot be shed by rule 3.
 Only hard rune-truncation, below every listed step, can reach either.
 
 Within a per-provider rule the steps run **tail-first** over the canonical
-provider order (Claude, Codex, Antigravity), so the provider a user reads first
-is the last to lose detail. This is why a 120-cell budget renders
-`Claude 5h [bar] · weekly [bar]   Codex 5h [bar]   Antigravity~~ weekly [bar]`
-— Codex's second window paid for Claude's — where whole-segment tier selection
-dropped both second windows at once and rendered 92 cells into a 120-cell row.
+provider order (Claude, Codex), so the provider a user reads first
+is the last to lose detail. This is why a 100-cell budget renders
+`Claude 5h [bar] · weekly [bar]   Codex 5h [bar]` — Codex's second window paid
+for Claude's — where whole-segment tier selection would drop both second
+windows at once.
 
 The order lives in **exactly one place in code**: `usageShedOrder` in
 `internal/app/usagecmd/usage.go`. The entry names above are that variable's
@@ -351,18 +350,16 @@ the queued notify segment, not to the separate window-list live attention badge.
 the cached usage state in-process and aligns model/window rows with
 right-aligned numeric values, dims unavailable values, keeps stale sync/age
 metadata muted, and colors only threshold values: amber at 80% and red at 95%.
-Antigravity rows keep conversation-local `context` separate from account
-`quota/<exact upstream bucket ID>` rows; the popup displays an absolute reset
-when provided and otherwise the exact optional relative reset seconds. Opaque
-bucket IDs are escaped for terminal/tmux safety and are never assigned a
+Named `quota/<exact upstream bucket ID>` rows display an absolute reset when
+provided and otherwise the exact optional relative reset seconds; cached
+Antigravity rows from the removed adapter are not shown, and an enabled
+Antigravity appears only as an `usage unsupported` row. Opaque bucket IDs are escaped for terminal/tmux safety and are never assigned a
 `5h`/`weekly` cadence. Claude retains aggregate `5h`/`weekly` rows alongside
 typed named/model `limits[]` rows in this popup: model-scoped rows display the
 exact upstream group plus model display identity with a bounded terminal-safe
 label, reset, and per-row age. The compact status line excludes every Claude
 named/model row and continues to use only the aggregate official windows.
-Session State inspection lives under `Projects > Sessions > State`; global
-Settings > Session State is settings-only and the statusbar no longer exposes a
-duplicate State button.
+The statusbar has no State button.
 
 The path popup uses the native picker frame chrome, a one-line title,
 the full wrapped current path, cheap project/git metadata when available, and

package/docs/testing.md

@@ -7,6 +7,8 @@ and humans run the same entrypoints.
 
 - `make test` runs the fast Go unit suite. These tests avoid tmux, TTY, GUI,
   and host shell dependencies.
+- `make vet` runs `go vet ./...`. CI runs it in the Unit Tests job after
+  `make test`.
 - Picker unit coverage includes the backend-neutral item/action contract,
   native title-focused filtering, numeric selection, and shared close actions.
 - `make test-integration` builds `test/docker/Dockerfile` and runs
@@ -40,6 +42,19 @@ and humans run the same entrypoints.
   runner is slow or loaded; a wait that expires still fails with the description
   of what it was waiting for, so a slow machine reports a timeout rather than
   the regression message of the assertion that would have run next.
+- `make test-e2e-update` runs `test/e2e/update-flow.sh` in the Node image
+  (`test/docker/Dockerfile.node`) on a bridged network. It installs an older
+  published `projmux` from the public npm registry, runs the source build's
+  `update apply`, and asserts the global install reaches the latest published
+  version while the exact legacy tmux server, socket, and sessions survive,
+  then checks npm installer autodetection from an npm-shaped path. Because it
+  depends on the public registry and the published package, it is not a
+  required check and stays out of the aggregate `Test`: the separate
+  `Update Flow E2E` workflow runs it on pull requests that change the update
+  path, daily on a schedule, and on manual dispatch. A local run skips when the
+  registry is unreachable; under CI (`CI=true`) or
+  `PROJMUX_UPDATE_FLOW_STRICT=1` the script runs with `--strict`, where a skip
+  fails the run instead.
 - `make test-e2e-contract`, `make test-e2e-reliability`, and
   `make test-e2e-shards` validate typed attempt evidence, bounded semantic
   waits/owned cleanup, and exhaustive four-shard isolation without rerunning

package/docs/tmux-surface-inventory.md

@@ -10,7 +10,6 @@ Primary production sources:
 
 - `internal/integrations/mux/`
 - `internal/integrations/tmux/`
-- `internal/integrations/sessionstate/`
 - `internal/app/`
 - generated config from `projmux config render standalone`,
   `projmux config render app`, and `projmux shell`
@@ -79,7 +78,7 @@ focus resolution, preview, and recent-window inventory.
 
 The typed `internal/integrations/tmux.Client` owns higher-level operations
 such as ensure/open/kill sessions, recent session summaries, preview inventory,
-resource inventory, and session-state capture/replay.
+and resource inventory.
 
 ## Generated Configuration Surface
 
@@ -87,7 +86,7 @@ The standalone and app configs own:
 
 - app/runtime marker options such as `@projmux_app`;
 - status rows, ranges, palette options, mouse dispatch, and popup bindings;
-- AI, attention, notify, recent-window, session-state, and resource hooks;
+- AI, attention, notify, recent-window, and resource hooks;
 - project-root and live-resource options;
 - reload/apply behavior for default and named sockets.
 
@@ -102,11 +101,11 @@ integration or e2e coverage when live tmux behavior changes.
 | Identity | `display-message -p`, `list-clients -F` | focus, switch, hooks |
 | Pane/window inventory | `list-panes -a -F`, `list-windows -F` | preview, notify, attention, recent windows |
 | Session lifecycle | `has-session`, `new-session`, `attach-session`, `switch-client`, `kill-session` | attach, switch, sessions |
-| Split/window creation | `split-window`, `new-window` | AI split, shell, session restore |
+| Split/window creation | `split-window`, `new-window` | AI split, shell, Project materialization |
 | Metadata | `set-option -p`, `show-options`, `display-message` | AI state, labels, app ownership |
-| Hooks | `set-hook`, `show-hooks`, `run-shell -b` | notify, attention, autosave, recent windows |
+| Hooks | `set-hook`, `show-hooks`, `run-shell -b` | notify, attention, recent windows |
 | Interactive UI | `display-popup`, `capture-pane`, `resize-pane` | popup surfaces, title watch, layout |
-| State replay | `rename-window`, `select-layout`, `select-pane`, `send-keys` | session state |
+| Topology materialization | `rename-window`, `select-layout`, `select-pane`, `send-keys` | Project Continue and Registry reconcile |
 | Config | `source-file`, global/session options | install, apply, shell |
 | Resource inventory | `list-panes -a -F` with PID/TTY/project fields | Linux resource attribution |
 
@@ -121,7 +120,6 @@ Changes to this surface should preserve the repository validation order:
 5. `make test-integration`;
 6. `make test-e2e`.
 
-The maintained test list in [agent-workflow.md](agent-workflow.md) must change
-with behavior. Live tests must use isolated tmux sockets and must validate
-returned ids or queried server state rather than pane ordering, screen content,
-or `send-keys` as a completion signal.
+Live tests must use isolated tmux sockets and must validate returned ids or
+queried server state rather than pane ordering, screen content, or `send-keys`
+as a completion signal.

package/docs/troubleshooting.md

@@ -126,10 +126,8 @@ history without a current activation is excluded. A complete comparison with no
 mismatches emits no comparison block. An unreadable Registry or missing,
 inconsistent, orphaned, or unobservable activation produces an `unavailable` or
 `incomplete` enumeration signal; confirmed mismatches remain visible alongside
-those gaps. A foreign Codex state domain, opaque generation, or a present or
-unreadable generation pool is unobservable from the default daemon probe.
-Private pool generations can also have version-shaped IDs, so Doctor does not
-infer their running endpoint from that spelling or from admission-current.
+those gaps. A foreign Codex state domain or an opaque generation is
+unobservable from the default daemon probe.
 
 The additive `codex_endpoint_mismatch` JSON field carries the same mismatch set,
 enumeration gaps, and evidence strength without changing the schema version.

package/docs/upgrading.md

@@ -52,6 +52,141 @@ still requires an explicit `PROJMUX_INSTALLER=github-release`.
 
 ## Behavior Changes
 
+### Closed Project startup setting removed
+
+The closed-Project startup screen is now shown for every registered Project
+that has no running session, and it is never shown for a folder that is not a
+registered Project -- Enter registers and opens that folder in one step.
+With nothing left to choose, the setting that turned the screen off is gone.
+
+- Settings > Projects > Project Sidebar > Closed Project startup is removed.
+  Project Sidebar keeps its Runtime diagnostics choice.
+- `~/.config/projmux/sidebar-startup-picker` is no longer read. The first
+  `projmux config apply` after upgrading (which `make install` and
+  `projmux update apply` also run) removes it and prints one
+  `reclaimed retired closed-Project startup setting: removed 1 file` line.
+  Only a regular file with that name is removed; a failure is reported and
+  never fails the apply, and later applies print nothing.
+- **A saved `off` is not migrated.** If you had turned the screen off, a
+  registered closed Project shows it again. Its default row is Continue
+  project, so Enter opens the Project the way `off` did.
+- The second row is renamed from **Recreate Project** to
+  **Clear layout and open** (ko-KR: **구성 비우고 새로 열기**). It clears only
+  the Project's saved Window and Agent layout; the folder, its files,
+  `.projmux/config.toml`, and trust stay. Its confirmation screen uses the same
+  name, and its cancel row is **Keep the saved layout**. What the row does is
+  unchanged.
+- `switch sidebar-open --mode fresh` keeps its token, so a sidebar started by
+  an older client still reaches the renamed row's action.
+
+### Antigravity statusLine support removed
+
+projmux no longer installs, reads, or judges the Antigravity `statusLine` in
+`~/.gemini/antigravity-cli/settings.json`. Only the official hooks entry
+(`projmux` in `~/.gemini/config/hooks.json`) remains.
+
+- The first `projmux config apply` after upgrading (which `make install` and
+  `projmux update apply` also run) removes only a `statusLine` whose `command`
+  carries the `projmux-managed:antigravity-statusline:v1` marker, whatever its
+  `enabled`, `stack_with_default`, extra keys, or executable path. The rest of
+  the file keeps its bytes and mode. It is never re-installed, and
+  `projmux agent integrate antigravity` never creates or writes the file.
+  `agent integrate antigravity --remove` also removes the marker entry.
+- A user-owned `statusLine`, or any value without the marker, is left
+  untouched and can no longer block install, cause a conflict, or change the
+  doctor status. A malformed or unreadable settings file is skipped.
+- Until that removal runs, a leftover bridge calling
+  `internal agent-hook ingest antigravity-hook --event Statusline` exits 0 with
+  empty stdout and changes nothing.
+- Antigravity usage display (`agent usage`, the statusbar HUD and popup, and
+  the Settings usage rows), the Antigravity approval-required notification,
+  and the mid-turn busy detail are gone until Antigravity offers official
+  events for them. `agent usage --model antigravity` is still accepted and
+  prints the `usage unsupported` note; `agent capabilities` reports Antigravity
+  usage as unsupported. Working state still follows the official
+  `PreInvocation`/`Stop` hooks.
+- Leftover `~/.config/projmux/statusbar-visibility-*antigravity*` files,
+  `<state>/usage/antigravity-*.json` sidecars, and cached Antigravity rows in
+  `snapshots.json` are ignored, not deleted. Doctor JSON no longer has
+  `statusline_config_path`, and the diagnostic is named `Antigravity hooks`.
+
+### Project snapshots removed
+
+`registry.json` is now the only saved Project state. projmux no longer saves or
+restores Project snapshots anywhere else, so these surfaces are gone:
+
+- the `create snapshot`, `get snapshots`, `delete snapshot`,
+  `restore snapshot`, and `prune snapshot` commands. `create`, `get`,
+  `delete`, and `prune` now refuse the `snapshot` kind with a usage error. The
+  `restore` command group had no other child and is removed with them, so
+  `restore snapshot` fails as an unknown command. `prune` now prunes only stale
+  Projects and Agents;
+- the hidden `session-state` route;
+- the Global and Project **Snapshots** pages in Settings: the auto-save toggle
+  and interval, the per-Project auto-save override, and the save latest, save
+  named, preview, and delete actions;
+- the snapshot view in the session popup and its `SessionPopup:OpenState`
+  keybinding;
+- the session-state section of `projmux doctor`, including
+  `doctor --section session-state` and the `session_state_resume` and
+  `session_state_prune` JSON fields.
+
+projmux no longer emits `session-state.outcome` diagnostics records. Records
+with that event in existing logs are still read and accepted.
+
+The existing `${XDG_STATE_HOME:-$HOME/.local/state}/projmux/sessions` directory
+is no longer read. `projmux config apply` (which `make install` runs) removes
+the `*.json` snapshot files in it once, along with the `sessionstate-autosave`
+and `sessionstate-autosave-interval` files and the
+`sessionstate-projects/<session>/autosave` files under the config directory,
+and then removes the `sessions/` and `sessionstate-projects/` directories if
+they end up empty. It only removes regular files with those names and never
+follows symlinks. Any other entry there is kept, and the apply that removes
+the files lists it on its one `reclaimed retired Project snapshot files: ...`
+line; later applies with nothing left to remove print nothing. To keep the old files,
+copy those directories before you upgrade. `PROJMUX_SESSIONSTATE_AUTOSAVE` is
+ignored. Tmux configs rendered by older installs may
+still call `projmux internal tmux autosave-session-state`; that route stays and
+exits 0 without writing anything.
+
+Closed Projects start from the Registry: **Continue project** materializes the
+Project's stored Windows and Panes, and **Recreate Project** (since renamed
+**Clear layout and open**) replaces them with a fresh graph.
+Settings > Projects > Project Sidebar > Closed Project startup and its
+`sidebar-startup-picker` file were unchanged by that release; a later release
+removed them
+([Closed Project startup setting removed](#closed-project-startup-setting-removed)).
+Settings no longer saves a
+named layout from a live session into `<project>/.projmux/layouts`, and no
+current surface opens those files.
+Leftover `.projmux/layouts` files on disk and layout entries in
+`trusted-projects.json` are kept and ignored.
+
+### Private Codex generation files reclaimed
+
+The private Codex generation pool is gone; app-server lifetime belongs to
+`codex app-server daemon`. Nothing reads the files that pool left on disk, and
+`projmux config apply` (which `make install` and `projmux update apply` also
+run) removes them once:
+
+- under `${XDG_STATE_HOME:-$HOME/.local/state}/projmux/codex-generations/`:
+  `rolling-upgrade.json` and its `.flock`, the stored `qualification/*.json`
+  records, and the leased release bundles in `bundles/sha256-<digest>/`, which
+  are the bulk of that directory;
+- under `${XDG_STATE_HOME:-$HOME/.local/state}/projmux/g/<key>/`: each private
+  host's `.projmux-launch-<generation>.json` intent, its `.guard`, and the
+  app-server socket nothing listens on anymore.
+
+Each directory is removed once it ends up empty. Only entries whose names have
+exactly those shapes are removed, and symlinks are never followed. A private
+host whose socket still accepts a connection keeps its whole directory and is
+named on the report line instead, so an app-server that outlived projmux does
+not lose the socket under it. Any other entry is kept and listed on the single
+`reclaimed retired Codex generation files: ...` line that apply prints; later
+applies with nothing left to remove print nothing. A failure is reported on
+that line and never fails the apply, and a rerun converges. To keep the old
+files, copy those directories before you upgrade.
+
 ### Claude dialogue endpoint revalidation
 
 The heterogeneous dialogue release moves the public message envelope and
@@ -124,8 +259,7 @@ That is evidence of incompatibility, not permission to proceed. Operators must
 refuse a binary-only downgrade before installation and must not permit the old
 binary to write final-v2 bytes. To roll back during the prerelease window, stop
 the final writer, restore the exact pre-normalization Registry backup, and
-restore the matching intermediate binary as a pair. Snapshots are not migration
-or rollback inputs and are never rewritten by this normalization.
+restore the matching intermediate binary as a pair.
 
 Rollback rehearsal is byte-oriented: record the backup path, mode, SHA-256,
 and matching pre-release binary revision; stop every final-v2 writer; atomically
@@ -346,7 +480,7 @@ commands and exit 1. Use `internal ...` for generated plumbing and `config
 render|apply` for public configuration work.
 
 The mixed roots retain only `attach project`, `focus project|window|pane`, `pin
-project`, and `prune project|snapshot`. Shortcuts and singular/plural resource
+project`, and `prune agent|project`. Shortcuts and singular/plural resource
 kind aliases are unchanged. The ledger contains the complete removed
 argv/replacement/error matrix.
 
@@ -359,8 +493,8 @@ queue maintenance.
 
 ### Managed Agent hook producer migration
 
-The installer now writes Codex, Claude, Antigravity named hooks, Antigravity
-Statusline, and the tmux bell fallback with the canonical
+The installer now writes Codex, Claude, Antigravity named hooks, and the tmux
+bell fallback with the canonical
 `projmux internal agent-hook ingest ...` entrypoint. Copyable integration
 commands use `projmux agent integrate <provider>`.
 
@@ -374,8 +508,9 @@ through v0.11.1 before the next release when you need the migration-window
 event guarantee.
 
 Migration is ownership- and transaction-aware. Codex managed blocks and the
-Claude, Antigravity, Statusline, and tmux-bell markers are the only ownership
-evidence. Missing integrations and markerless commands are not installed or
+Claude, Antigravity, and tmux-bell markers are the only ownership
+evidence (the legacy Antigravity statusLine marker is only ever removed; see
+[Antigravity statusLine support removed](#antigravity-statusline-support-removed)). Missing integrations and markerless commands are not installed or
 rewritten. Provider file plans and conflicts are collected before the first
 file write. Live bell state is then inventoried on the exact target socket
 before its first command; a later bell failure rolls back both that live state

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
@@ -355,7 +331,7 @@ When a collection fails, the failure is visible in three places:
    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
+   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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projmux",
-  "version": "0.15.3",
+  "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.3",
-    "@projmux/linux-arm64": "0.15.3",
-    "@projmux/darwin-x64": "0.15.3",
-    "@projmux/darwin-arm64": "0.15.3"
+    "@projmux/linux-x64": "0.16.0",
+    "@projmux/linux-arm64": "0.16.0",
+    "@projmux/darwin-x64": "0.16.0",
+    "@projmux/darwin-arm64": "0.16.0"
   }
 }