projmux 0.10.0 → 0.11.0

package/docs/configuration.md

@@ -106,10 +106,11 @@ language.
 
 Settings > Keybindings is the normal in-app editor for action keys. It lists
 actions with the current active keys and one state: Default, Custom, Available,
-or Unbound. Open an action to see the action label, state, a flat Keys list,
-Options, and a collapsed Troubleshooting row. Create flows start from
-`+ Add key`, deletion lives under each key's detail, and action-level state
-changes such as Unbind or Reset live under Options. Successful saves report the
+or Unbound. Open an action to see the action label, state, the action's
+target/result/placement/anchor and shipped handler, a flat Keys list, and
+Options. Create flows start from `+ Add key` or `Enter key name manually`,
+deletion and `Test delivery` live under each key's detail, and action-level
+state changes such as Unbind or Reset live under Options. Successful saves report the
 keybinding as saved; failures identify the stage that failed.
 
 Raw sequences that cannot be safely represented as a direct keybinding are not
@@ -124,16 +125,19 @@ absent, generated tmux config stays on the built-in defaults.
 Supported schema:
 
 ```toml
-[bindings.ProjectSidebarToggle]
+schema_version = 2
+
+[bindings."project-sidebar.toggle"]
 keys = ["M-1", "M-a"]
+sequences = ["C-k C-p"]
 
-[bindings.new-window]
+[bindings."window.create"]
 keys = ["C-t"]
 
-[bindings."Sidebar:PinProject"]
+[bindings."project-sidebar.project.pin-toggle"]
 keys = ["M-p", "p"]
 
-[bindings."Resources:Open"]
+[bindings."resource-inspector.open"]
 keys = ["M-u"]
 ```
 
@@ -143,6 +147,21 @@ Each table is `[bindings.<action-id>]`. Supported keys are:
 | --- | --- |
 | `keys` | A list of no-prefix tmux plain chords such as `M-a`, `C-t`, or `M-S-Left`. |
 | `plain` | Legacy single-primary replacement. Still read, but not written by Settings. |
+| `sequences` | Additive two-to-four-stroke triggers such as `C-k C-p`; manual-file/runtime support only in Phase 0. |
+
+The root `schema_version` marker is the file's own version. A file without one
+is v0 and uses the runtime action ids (`ProjectSidebarToggle`, `new-window`,
+`Sidebar:PinProject`); v1 uses canonical dotted ids, and
+`schema_version = 2` adds `sequences`. All versions read — the v0 spelling of
+every action is a permanent read alias — and migration to v2 runs at
+`projmux config apply` or at the first Settings key save. A v1 migration is a
+marker-only edit with a digest-named pre-v2 backup. [docs/keybindings.md](keybindings.md#schema-versions) has the full
+table, the upgrade ordering and the downgrade procedure.
+
+This marker is a separate version domain from the CLI resource registry's
+`apiVersion: projmux.io/v1alpha1` / camelCase `schemaVersion: 1` envelope. The
+two have separate markers, separate backups and separate rollbacks; neither one
+failing affects the other.
 
 Legacy `prefix = ...` entries still parse during migration so existing files
 do not break. Settings preserves existing prefix entries when rewriting the
@@ -159,21 +178,22 @@ Use an empty `keys` list to disable direct plain keys for the action when
 editing the file by hand:
 
 ```toml
-[bindings.ProjectSidebarToggle]
+[bindings."project-sidebar.toggle"]
 keys = []
 ```
 
 In Settings, reset removes the saved override and returns to the built-in
-default. Legacy popup IDs such as
-`sessionizer-sidebar` still read, but new writes use canonical toggle names
-such as `ProjectSidebarToggle`, `NotifySidebarToggle`, `SessionPopupToggle`,
-`AISplitPickerToggle`, `SettingsToggle`, and `ProjectSwitcherToggle`. Internal
-popup commands use `Surface:Action` IDs and have surface-local conflict
-domains and remain visible in Settings when catalogued.
-
-`Resources:Open` is a user-configurable direct popup action with no built-in
-shortcut. Every configured alias renders the canonical client-scoped body
-`projmux tmux popup-toggle --client #{client_tty} resource-inspector`; pressing
+default. Popup *mode* names such as `sessionizer-sidebar` are not action ids and
+resolve to nothing; a migration preserves such a table and reports it rather
+than remapping it. Internal picker commands keep surface-local conflict domains
+under their canonical ids (`session-picker.*`, `notification-sidebar.*`,
+`project-sidebar.*`, `settings.*`) and remain visible in Settings when
+catalogued.
+
+`resource-inspector.open` (v0 `Resources:Open`) is a user-configurable direct
+popup action with no built-in shortcut. Every configured alias renders the
+canonical client-scoped body
+`projmux internal tmux popup-toggle --client #{client_tty} resource-inspector`; pressing
 the same alias again closes only that client's popup. It remains available on
 Linux/tmux even when the Labs live-resource status segment is off.
 
@@ -181,9 +201,11 @@ The Settings writer is deterministic and rewrites the supported saved subset
 only. If the existing file has parse errors or unknown action IDs, Settings
 shows the keymap error row and refuses to overwrite it until the file is fixed.
 
-The file currently affects generated tmux config from `projmux tmux
-print-config`, `projmux tmux install`, `projmux tmux print-app-config`,
-`projmux tmux install-app`, and `projmux shell`. Terminal remediation adapters such as
+The file currently affects generated tmux config from `projmux config render
+standalone`, `projmux config render app`, `projmux config apply`, the hidden
+`projmux internal tmux install` / `install-app` installer plumbing, and `projmux shell`.
+The render routes never write the keymap; `projmux config apply` migrates it
+first and only applies once that succeeds. Terminal remediation adapters such as
 Ghostty and Windows Terminal install built-in plain-byte mappings where needed;
 they do not read `keymap.toml` or copy saved keys into terminal configs.
 Changing terminal-layer mappings still requires rerunning `projmux setup
@@ -210,7 +232,7 @@ field with source labels: `global` or `fallback`. Saving or resetting a theme
 value live-applies it: projmux regenerates the generated tmux config and, when
 Settings runs inside tmux, `tmux source-file`-reloads it so a running server
 repaints immediately. Outside tmux the save still succeeds and the report
-prints `Next: run \`projmux tmux apply\`` to sync a running server.
+prints `Next: run \`projmux config apply\`` to sync a running server.
 
 The `background`, `surface`, `status_background`, `surface_active`, and
 `pane_active_bg` tokens additionally accept the value `default` ("Terminal
@@ -251,7 +273,7 @@ rectangle is not guaranteed; focus is reinforced by the tint plus the
 `pane-border-status top` topic line. This chrome preserves `pane-border-status
 top`, pane topics, AI badges, and visible pane labels.
 
-Native picker popups launched through `projmux tmux popup-toggle` also pass a
+Native picker popups launched through `projmux internal tmux popup-toggle` also pass a
 per-popup tmux 3.4 `display-popup -s` body style using the effective theme
 `surface` / `chrome_foreground` tmux tokens (popup/native backgrounds follow
 `surface`, while the bottom status bar follows `status_background`). This styles
@@ -360,7 +382,7 @@ user/global preference in this release.
 
 ## AI Resume Picker
 
-The AI resume picker (`projmux ai split --agent resume`) lists the most recent
+The Agent resume picker lists the most recent
 deduplicated Claude/Codex/Antigravity resume sessions. The number of rows it
 shows and how far below the current directory it scans are both configurable;
 the defaults are 30 rows and depth 0 (the current directory only).
@@ -430,11 +452,11 @@ confidence for DB-validated cache sources or low confidence for legacy history.
 | `PROJMUX_AI_RESUME_SCAN_DEPTH` | Overrides the AI resume picker cwd-tree scan depth (`[ai] resume_scan_depth`). Clamped to 0-8; takes priority over project and global config. Depth 0 keeps the exact-cwd behavior. |
 | `PROJMUX_NOTIFY_HOOK_DEPTH` | Internal recursion guard for `send-noti` hooks. Depth `>= 1` suppresses nested hook dispatch while still allowing the queue write itself. |
 | `PROJMUX_NOTIFY_EXPIRE_MS` | AI desktop notification expiration in milliseconds. Defaults to `5000`; unset, zero, negative, and non-numeric values fall back to the default. |
-| `PROJMUX_DESKTOP_NOTIFY_MODE` | OS desktop notification mode override. `none` / `notify` / `raise` (case insensitive). When set, this takes priority over every other resolution rung. The in-app notify queue is not affected. |
+| `PROJMUX_DESKTOP_NOTIFY_MODE` | OS desktop notification mode override. `off` / `none` / `notify` (case insensitive). When set, this takes priority over every other resolution rung. The in-app notify queue is not affected. The retired `raise` / `auto-raise` / `autoraise` literals are still accepted and read as `notify`. |
 | `PROJMUX_DESKTOP_NOTIFY` | Legacy on/off override kept for backward compatibility. `on` maps to `notify`, `off` maps to `none`. Honored only when `PROJMUX_DESKTOP_NOTIFY_MODE` is unset. |
 | `PROJMUX_WSL_TOAST_ICON_DIR` | Directory used when copying the WSL toast icon into a Windows-readable path. |
 | `PROJMUX_USAGE_STATE_DIR` | Override directory for AI usage snapshots. Defaults to `<state>/projmux/usage`. Point this at a synced directory to share authoritative usage across machines. |
-| `PROJMUX_USAGE_DEBUG` | When non-empty, prints adapter errors from `projmux status usage` to stderr. |
+| `PROJMUX_USAGE_DEBUG` | When non-empty, prints adapter errors from the `projmux internal status usage` renderer to stderr. |
 | `PROJMUX_USAGE_LIMITS_PATH` | Deprecated. Read but ignored; limits now come from upstream APIs and local Codex rollout state. |
 | `PROJMUX_SESSIONSTATE_AUTOSAVE` | Session snapshot autosave override for the global fallback. Values such as `off`, `false`, or `0` disable autosave for projects that inherit the global setting; explicit project auto-save `on`/`off` still takes precedence. |
 | `PROJMUX_SESSIONSTATE_DEBUG` | When non-empty, quiet autosave surfaces suppressed session-state errors to stderr. |
@@ -534,7 +556,7 @@ host setup.
 - `[hooks.send-noti]` fires after the queue write and does not replace desktop
   notifications.
 - `PROJMUX_NOTIFY_HOOK_DEPTH` prevents a `send-noti` hook that calls
-  `projmux notify push` from recursively re-triggering itself.
+  `projmux create notification` from recursively re-triggering itself.
 
 The app-name argument is `com.crevisse.projmux` (reverse-domain id used as
 the Linux `--app-name`, the macOS sender label, and the Windows
@@ -561,10 +583,10 @@ AI hook runtime actions are stored at:
 ${XDG_CONFIG_HOME:-$HOME/.config}/projmux/ai-hook-actions.json
 ```
 
-Settings exposes this at `Settings > Notifications > Hook quiet policy`.
+Settings exposes this at `Settings > Notifications > Agent event behavior`.
 The file maps provider/event names to `notify`, `state`, or `quiet` and
 overrides catalog `action` values during ingest, including known Codex and
-Claude events. It does not change hook installation; `projmux ai integrate`
+Claude events. It does not change hook installation; `projmux agent integrate`
 continues to use the embedded/local catalog `install` fields.
 
 Delivery depends on the event handler. Specialized notify handlers, such as
@@ -576,40 +598,42 @@ only a generic in-app queue/sidebar/statusbar row; it does not fire OS toast,
 
 ### Desktop notification mode
 
-The OS-level dispatch carries three modes. The in-app notify queue, the
+The OS-level dispatch carries two modes. The in-app notify queue, the
 statusbar segment, and the attention badge stay live regardless of which
-mode is active — only the toast / notify-send / auto-raise fan-out is
-gated here. The same mode also gates `projmux focus` post-switch osfocus
-dispatch: only `raise` asks the host terminal to come forward after a
-successful tmux focus.
+mode is active — only the toast / notify-send fan-out is gated here.
 
 | Mode | On push | On click |
 | --- | --- | --- |
 | `off` / `none` | no toast | n/a |
 | `notify` | toast / notify-send fires | no click action |
-| `raise` | toast / notify-send fires AND the host terminal is auto-raised via the osfocus chain | toast click invokes `projmux focus --uri` via the `projmux://` handler |
 
-Click activation is wired only for `raise`. The `projmux://` URI handler is
-registered on the first `raise` Notify of each tmux server (gated by the
-`@projmux_uri_protocol_registered_v6` marker). The
-mode only controls whether a toast fires at all and whether to follow it
-up with an on-push auto-raise. `off` / `none` and `notify` also suppress
-the focus-triggered osfocus raise after `projmux focus`.
+Desktop notification delivery never takes your host terminal window focus.
+The Toast carries no `launch` payload, projmux registers no `projmux://`
+protocol handler, and there is no auto-raise on push. `projmux focus` also
+stops at the tmux layer in every mode: it switches the client, window, and
+pane but never asks the host terminal window to come forward.
 
 Resolution order (highest priority first):
 
-1. `PROJMUX_DESKTOP_NOTIFY_MODE` env (`off` / `none` / `notify` / `raise`).
+1. `PROJMUX_DESKTOP_NOTIFY_MODE` env (`off` / `none` / `notify`).
 2. `PROJMUX_DESKTOP_NOTIFY` env (legacy `on` / `off`; `on` → `notify`,
    `off` → `none`).
 3. Saved Settings config
    `${XDG_CONFIG_HOME:-$HOME/.config}/projmux/desktop-notify-mode`
-   (`off` / `notify` / `raise`).
+   (`off` / `notify`).
 4. Tmux global option `@projmux_desktop_notify_mode`.
 5. Tmux global option `@projmux_desktop_notify` (legacy `1` / `0`, same
    mapping as the env above).
-6. Default = `raise` when running inside WSL with `$WT_SESSION` set
-   (Windows Terminal × WSL is the measured-working cell for osfocus
-   raise today); otherwise `notify`.
+6. Default = `notify` on every platform, WSL + Windows Terminal included.
+
+The retired `raise` mode was removed in 0.11.0. Wherever a mode literal is
+read — env, saved file, or tmux option — `raise`, `auto-raise`, and
+`autoraise` are still accepted and resolve to `notify` **in that same
+source**, so an old value keeps pinning the resolution instead of falling
+through to a lower-precedence rung. The alias never re-enables host-window
+focus, a clickable Toast, or URI handler registration; it is not offered in
+Settings and is never written back — the first Settings press or
+`projmux config apply` replaces it with `notify`.
 
 Migration is intentionally read-time. Users with the previous legacy
 toggle set keep their behavior — `@projmux_desktop_notify=0` resolves to
@@ -621,97 +645,41 @@ legacy key unused. No eager rewrite of tmux state.
 Toggle from Settings > Notifications > `Desktop notifications`. The
 Settings info row labels the effective source as `env`, `env (legacy)`,
 `setting`, `setting (legacy)`, or `default` so users see which rung of
-the cascade pinned the value. `projmux tmux apply` regenerates the live tmux
+the cascade pinned the value. `projmux config apply` regenerates the live tmux
 option from the saved Settings file; when that file is missing, apply writes
 only the default for the current host.
 
 Hook details for new-session lifecycle hooks and project-local
 `.projmux/config.toml` live in [Hooks](hooks.md).
-Settings names that entry point as **Project recipe** (search still matches
-`config.toml` as an alias) to avoid leaking internal file names in the primary
-Settings view.
+Settings exposes project-local executable automation under **Project >
+Automation**. `[startup]` and generic `[env]` remain config-file compatibility
+inputs and are not Settings authoring destinations.
 
-### Toast click handler (WSL + Windows Terminal)
+### Toast click handler (WSL + Windows Terminal) — retired in 0.11.0
 
-On WSL, projmux registers a `projmux://` URL scheme on the Windows side
-the first time a Toast is dispatched on each tmux server. Clicking the
-toast hands control back to projmux inside WSL via the registered command:
+projmux used to register a `projmux://` URL scheme on the Windows side and
+emit clickable Toasts whose click routed through the hidden `projmux internal focus` ingress.
+That path is **removed**: desktop notifications are passive, carry no
+`launch` payload, and projmux registers no protocol handler. Clicking a
+projmux Toast does nothing.
 
-```text
-wscript.exe //B //Nologo "%LOCALAPPDATA%\projmux\projmux-uri-handler.vbs" "%1"
-```
+Consequences for existing installs:
 
-Registration writes the VBScript launcher under `%LOCALAPPDATA%\projmux`.
-The launcher receives `%1` as a WScript argument, caret-escapes command-line
-metacharacters such as `&`, and starts a hidden `%ComSpec% /d /s /c` command
-that invokes `wsl.exe`. Its argv semantics are equivalent to:
-
-```text
-wsl.exe -d $WSL_DISTRO_NAME --exec <absolute-path-to-projmux> focus --uri <uri>
-```
+- A `HKCU\Software\Classes\projmux` key written by an earlier version is
+  **not** removed automatically. Delete it manually if you want the scheme
+  gone; leaving it in place is harmless because nothing produces the URI.
+- The old public `focus --uri` compatibility input is removed. Machine-owned
+  focus payloads use `projmux internal focus --uri`. No
+  projmux code path produces such a URI any more.
+- The `@projmux_uri_protocol_registered*` tmux markers are no longer read or
+  written. Stale markers are inert.
 
-For click activation to work in our unpackaged Win32 setup, four
-conditions must hold simultaneously — all of them are arranged by the
-notify path so users do not configure anything:
-
-1. No COM Toast Activator is registered. The shortcut writes only
-   `PKEY_AppUserModel_ID` (pid=5) and intentionally omits
-   `PKEY_AppUserModel_ToastActivatorCLSID` (pid=26). When a COM activator
-   is registered alongside the AppID, Windows tries COM first, silently
-   fails for unpackaged exes, and does *not* fall through to the launch
-   URI. Stripping the COM side makes Windows ShellExecute the launch URI
-   on click.
-2. The Start Menu shortcut exists with the AppID set. The shortcut is
-   never launched — it is a property bag so the toast can route under
-   the right DisplayName + icon.
-3. The shortcut target is `cmd.exe /c exit`. Earlier code used
-   `powershell.exe -WindowStyle Hidden -Command exit`; Windows Defender
-   silently quarantines such shortcuts moments after creation, which
-   leaves no AppID-tagged shortcut and breaks both the routing and the
-   click path. `cmd.exe /c exit` is treated as benign and survives.
-4. The WSL handler uses a WScript launcher instead of launching `wsl.exe` or
-   `powershell.exe` directly, avoiding the transient Windows console flash on
-   Toast click. Inside that launcher it still uses `--exec`, not `--`.
-   `wsl.exe -- <cmd>` routes its tail through the user's login shell, which
-   parses `&` query-string separators as background-job operators (zsh emits
-   `parse error near '&'`). `--exec` skips the shell and invokes the binary
-   directly. The `%1` URI is passed as a WScript argument and then forwarded
-   through a hidden cmd.exe command line with `&` escaped as `^&`, so query
-   separators are data instead of PowerShell, cmd, or WSL login-shell syntax.
-   The absolute WSL filesystem path to the binary is captured at registration
-   so PATH does not need to be populated under `--exec`.
-
-The URI carries the originating pane id and tmux socket so the click
-round-trips back to the exact pane that fired the notification, which
-the `projmux focus` path then redirects via `tmux switch-client`.
-
-Registration markers and the writes involved:
-
-- Registry keys (HKCU): `SOFTWARE\Classes\projmux\(Default)`,
-  `SOFTWARE\Classes\projmux\URL Protocol`, and
-  `SOFTWARE\Classes\projmux\shell\open\command\(Default)`.
-- Launcher file: `%LOCALAPPDATA%\projmux\projmux-uri-handler.vbs`.
-- tmux user-option marker `@projmux_uri_protocol_registered_v6` records that
-  registration has been attempted on this server so the script runs at most
-  once per server boot. (The v5 marker
-  `@projmux_uri_protocol_registered_v5` was bumped when the WScript launcher
-  added the hidden cmd.exe parser hop; existing v5 users re-register
-  transparently on the next Notify after upgrade. After successful v6
-  registration, projmux removes legacy URI marker keys from v1 through v5 so
-  tmux state reflects only the active handler generation.)
-
-Limitations:
-
-- The handler captures the user's current `WSL_DISTRO_NAME` at registration
-  time. Users running multiple WSL distros get one handler bound to the
-  first distro that fired a toast — clicks from a different distro's toast
-  will route back through the first distro. Tier-2 follow-up.
-- WSL2 cold-start latency: the first click after a long idle goes through
-  WSL boot and typically takes 2-3s to surface the focus on the pane.
+The measurement trail for the retired design is kept for history in
+[notify-os-focus-poc.md](notify-os-focus-poc.md).
 
 ## Usage Tracking
 
-`projmux usage` and the status-bar usage segment store snapshots under:
+`projmux agent usage` and the status-bar usage segment store snapshots under:
 
 ```text
 ${PROJMUX_USAGE_STATE_DIR:-${XDG_STATE_HOME:-$HOME/.local/state}/projmux/usage}/snapshots.json
@@ -776,10 +744,10 @@ The environment variables above override the global files.
 Manual snapshot actions are available from the CLI:
 
 ```sh
-projmux session-state status [--session <name>]
-projmux session-state save
-projmux session-state delete [--session <name>]
-projmux session-state restore --dry-run [--session <name>]
+projmux get snapshots
+projmux create snapshot
+projmux delete snapshot [--session <name>]
+projmux restore snapshot --dry-run [--session <name>]
 ```
 
 `status` prints the source label (`autosave`, `layout(<name>)`, or `fresh`), the
@@ -811,16 +779,98 @@ The per-surface saved values live at:
 The legacy `~/.config/projmux/statusbar-decoration` value is still read as the
 fallback default when a per-surface file is absent.
 
-## Live System Resources Lab
+## Row 0 HUD Visibility
+
+`Settings > Appearance > Status Bar` controls the two upper HUD components as
+independent global presentation preferences:
+
+- `Notifications HUD > Visible`
+- `Agent Usage HUD > Visible`
+- `Agent Usage HUD > Claude|Codex|Antigravity > Visible`
+- each provider's supported HUD windows (`Claude`/`Codex`: `5h`, `Weekly`;
+  `Antigravity`: `Weekly`)
+
+The saved values are `on` or `off` in these files:
+
+```text
+~/.config/projmux/statusbar-visibility-notifications-hud
+~/.config/projmux/statusbar-visibility-agent-usage-hud
+~/.config/projmux/statusbar-visibility-agent-usage-provider-claude
+~/.config/projmux/statusbar-visibility-agent-usage-provider-codex
+~/.config/projmux/statusbar-visibility-agent-usage-provider-antigravity
+~/.config/projmux/statusbar-visibility-agent-usage-window-claude-5h
+~/.config/projmux/statusbar-visibility-agent-usage-window-claude-weekly
+~/.config/projmux/statusbar-visibility-agent-usage-window-codex-5h
+~/.config/projmux/statusbar-visibility-agent-usage-window-codex-weekly
+~/.config/projmux/statusbar-visibility-agent-usage-window-antigravity-weekly
+```
+
+Missing, empty, and invalid values resolve to the compatibility default `on`;
+Settings shows whether the effective value came from `saved` or `default` and
+marks an invalid saved value as ignored. Saving a toggle regenerates the app
+and standalone tmux output, and Settings source-reloads the generated app config
+when it is running inside tmux.
+
+Parent visibility gates only the effective projection. Turning the overall HUD
+or a provider off does not rewrite its provider/window leaf files; turning the
+parent back on restores the saved child selection. Provider rows follow the
+usage-supported provider catalog. Window rows come only from the explicit HUD
+capability map, so opaque quota buckets never create settings and Antigravity
+never gains a fabricated `5h` row.
+
+Visibility does not enable or disable either producer. Hiding Notifications HUD
+does not change the persistent queue, desktop delivery, or Notification
+Sidebar. Hiding Agent Usage HUD does not change the `agent usage` command,
+Provider snapshot cache, upstream API collection, quota, or refresh policy.
+Provider/window leaves likewise filter only `projmux internal status usage`; explicit
+`agent usage` table/JSON and the cached statusbar popup remain lossless.
+
+## Row 1 Segment Visibility
+
+`Settings > Appearance > Status Bar` controls these retained lower-row
+components independently:
+
+- `Project`
+- `Working directory > Visible`
+- `Git > Visible`
+- `Clock`
+- `Settings launcher`
+
+Their global saved values are `on` or `off` in:
+
+```text
+~/.config/projmux/statusbar-visibility-project
+~/.config/projmux/statusbar-visibility-working-directory
+~/.config/projmux/statusbar-visibility-git
+~/.config/projmux/statusbar-visibility-clock
+~/.config/projmux/statusbar-visibility-settings-launcher
+```
+
+Missing, empty, and invalid values resolve to `on`; Settings reports the
+effective value and whether it came from `saved` or `default`. Each save is an
+atomic 0600 replacement, regenerates both app and standalone output, and
+source-loads the generated app config when Settings is inside tmux. Off removes
+the complete segment, including its mouse range and owned spacing. Working
+directory/Git icon mode remains a separate setting, so icon `off` leaves the
+text visible. Settings launcher `off` removes only its mouse chip; CLI and
+keybinding entry remain.
+
+Resources intentionally does not use one of these visibility files. Its
+existing `~/.config/projmux/live-resources` value is the only enabled source
+and controls both the segment and sampler/cache mutation.
+
+## Live System Resources
 
-`Settings > Labs > Live system resources` controls the experimental compact
+`Settings > Appearance > Status Bar > Resources` controls the compact
 CPU/memory segment on the lower status row. The saved global value is:
 
 ```text
 ~/.config/projmux/live-resources
 ```
 
-Accepted values are `off` (default) and `on`. The feature is available on
+Accepted values are `off` (default) and `on`. A missing, empty, or invalid
+saved value resolves to `off` with source `default`; valid saved values report
+source `saved`. The feature is available on
 macOS, native Linux, and WSL. Linux reads procfs directly; macOS reads Mach host
 statistics and `hw.memsize`. Neither path launches `top`, `vm_stat`, `free`,
 PowerShell, or another metrics process. On macOS, available memory is free plus
@@ -830,8 +880,9 @@ Windows host utilization. These are host-scoped values and do not attribute
 usage to a pane, window, project, or session.
 
 When enabled, the compact segment is also the clickable `resources` statusbar
-range and opens the Resource Inspector. Turning the Lab off hides only this
-segment; it does not disable `projmux resources` or a custom-bound
+range and opens the Resource Inspector. Turning Resources off hides the segment
+and stops its host sampler/cache writes; it does not disable the explicit
+`projmux resources` inspector or a custom-bound
 `Resources:Open` action. Inspector samples are memory-only for the popup
 lifetime and are unrelated to the status segment's host CPU reference cache.
 
@@ -858,5 +909,3 @@ These are intended for debugging or local policy, not routine setup:
 | `PROJMUX_TMUX_NOTIFY_DEDUPE_SECONDS` | Override the Settings/default collapse window for duplicate AI desktop notifications keyed on the pane-local AI notification key. |
 | `PROJMUX_CODEX_TITLE_WATCH_INTERVAL` | Title-watch loop pacing for Codex panes. |
 | `PROJMUX_CODEX_REPLY_SETTLE_LOOPS` | Reply-detection settle-loop pacing for Codex panes. |
-| `TMUX_KUBE_CACHE_TTL` | Kubernetes status segment cache TTL. |
-| `TMUX_KUBE_TIMEOUT` | kubectl invocation budget for the Kubernetes status segment. |

package/docs/globalization.md

@@ -34,7 +34,7 @@ Classification:
 
 | Family | Examples | Class | Phase 0 policy |
 | --- | --- | --- | --- |
-| Agent names | `Codex`, `Claude`, `AI` | `literal` | Preserve exactly. |
+| Agent names | `Codex`, `Claude`, `Antigravity`, `AI` | `literal` | Preserve exactly. |
 | Category labels | `Response complete`, `Approval required`, `Input required`, `Error`, `Subagent stopped`, `Teammate waiting` | `translate` | English baseline now; catalog keys later. |
 | Review body prefix | `Review pending:` | `translate` | English baseline now; catalog key later. |
 | Tool names | `Bash`, `Read`, `WebFetch`, `Shell` | `literal` | Preserve provider/source spelling. |
@@ -50,12 +50,13 @@ Files:
 - `internal/app/status.go`
 - `docs/statusbar.md`
 - `docs/cli.md`
+- `docs/cli-guide.md`
 
 Classification:
 
 | Family | Examples | Class | Phase 0 policy |
 | --- | --- | --- | --- |
-| CLI flag help and usage | `--text`, `--target`, `notify push`, usage errors | `translate` | Inventory only; convert in catalog phases. |
+| CLI flag help and usage | `--text`, `--target`, `create notification`, usage errors | `translate` | Inventory only; convert in catalog phases. |
 | Queue row labels and action hints | ack, clear, focus, open, reconcile labels | `translate` | Inventory only; convert in catalog phases. |
 | Statusbar compact text | notify count, age, stale/gone hints | `translate` | Inventory only; needs compact locale formatter later. |
 | Source/severity enum values | `ai`, `k8s`, `git`, `external`, `critical` | `literal` | Preserve exactly. |
@@ -78,8 +79,8 @@ Classification:
 | Row labels and previews | enabled/disabled state, current source, saved values | `translate` | Inventory only; catalog later. |
 | Disabled reasons and warnings | missing project, env override, conflict text | `translate` | Inventory only; catalog later. |
 | Config keys and env vars | `PROJMUX_PROJDIR`, `config.toml`, `ui.locale` | `literal` | Preserve exactly. |
-| Commands shown for copying | `projmux ai integrate codex --dry-run` | `literal` | Preserve exactly. |
-| Persisted values | `none`, `notify`, `raise`, `auto` | `literal` | Preserve enum values. |
+| Commands shown for copying | `projmux agent integrate codex --dry-run`, `projmux agent integrate antigravity --dry-run` | `literal` | Preserve exactly. |
+| Persisted values | `off`, `none`, `notify`, `auto` | `literal` | Preserve enum values. |
 
 ### Native Picker And Render Surfaces
 
@@ -108,6 +109,7 @@ Files:
 - `internal/app/settings*.go`
 - `internal/app/*help*`
 - `docs/cli.md`
+- `docs/cli-guide.md`
 - `docs/agent-workflow.md`
 
 Classification:
@@ -124,7 +126,7 @@ Classification:
 
 Do not translate these families:
 
-- Product and agent names: `Codex`, `Claude`, `projmux`, `tmux`,
+- Product and agent names: `Codex`, `Claude`, `Antigravity`, `projmux`, `tmux`,
   `GitHub`, `npm`.
 - Terminal and app names: `Windows Terminal`, `Ghostty`, `WezTerm`, `Kitty`,
   `iTerm2`, `Alacritty`, `Foot`.
@@ -239,7 +241,8 @@ Contribution convention:
 - Add the `en-US` entry in the same change as the key.
 - Add `ko-KR` when the translation is known; otherwise rely on fallback while
   keeping the missing key intentional in review notes.
-- Do not translate product names (`projmux`, `tmux`, `Codex`, `Claude`),
+- Do not translate product names (`projmux`, `tmux`, `Codex`, `Claude`,
+  `Antigravity`),
   commands, paths, config keys, environment variables, provider payloads, or
   source enum values.
 - Runtime migrations should be narrow by surface. Move a string family behind
@@ -296,9 +299,10 @@ Width-safe rendering:
 
 Runtime surfaces migrated:
 
-- AI desktop notification summaries for Codex and Claude hook payloads.
+- AI desktop notification summaries for Codex, Claude, and Antigravity hook
+  payloads.
 - In-app notify queue table/sidebar/statusbar display text for AI entries.
-- Notify live explanation text for `projmux notify list --live`.
+- Notify live explanation text for `projmux get notifications --live`.
 - Sidebar/table/statusbar age formatting and sidebar stale/gone/target labels.
 
 Storage and dispatch policy:
@@ -309,7 +313,7 @@ Storage and dispatch policy:
 - OS notification click/focus routing is unchanged. Locale formatting only
   changes the summary/body strings sent to the configured notifier.
 - JSON queue payloads keep raw queue entries. Localized live-row explanation
-  and row display text may appear in `notify list --live` row fields because
+  and row display text may appear in `get notifications --live` row fields because
   those fields are render/report output, not stored queue schema.
 
 Literal preservation and parity rules:
@@ -317,9 +321,9 @@ Literal preservation and parity rules:
 - Translate only catalog-owned category labels such as `Response complete`,
   `Approval required`, `Input required`, `Error`, `Subagent stopped`, and
   `Teammate waiting`.
-- Preserve provider-owned payloads verbatim: `Codex`, `Claude`, tool names,
-  commands, paths, URLs, query strings, transcript excerpts, teammate IDs, and
-  subagent IDs.
+- Preserve provider-owned payloads verbatim: `Codex`, `Claude`, `Antigravity`,
+  tool names, commands, paths, URLs, query strings, transcript excerpts,
+  teammate IDs, and subagent IDs.
 - Desktop notification summaries and in-app queue display text must use the
   same rendered category labels for the same locale while preserving the same
   literal payload body.