projmux 0.8.3 → 0.9.0

package/docs/settings-ia.md

@@ -11,6 +11,10 @@ view-first layout:
   current state, source, and expected rendered result before offering mutation
   rows. If a detail opens a dedicated `Change` page, that page is mutation-only
   and does not repeat the same read-only view rows.
+- Every rendered non-empty row value is classified as navigation, actionable,
+  or passive information/disabled state and is mapped to a closed owner-loop
+  contract before rendering. An unowned value is a Settings error; Enter on a
+  passive row is consumed as a no-op.
 - `Settings > Project Picker > Workdirs` is the list/overview entry. Add/remove
   actions live inside that view.
 - `Settings > Project Picker > Project Root` shows effective and saved values
@@ -35,7 +39,7 @@ view-first layout:
   rows as always-visible sections.
 - Terminal delivery remediation lives outside Settings primary flow. The
   supported order is `projmux shell` first, then `projmux setup`, then
-  `projmux init` for supported terminal adapters.
+  `projmux setup terminal` for supported terminal adapters.
 - Rows that cannot safely be edited still stay visible. Mark diagnostic-only
   rows with the delivery path and reason instead of hiding them or turning them
   into unsupported editable keys. Transport-dependent rows stay visible with
@@ -57,9 +61,10 @@ view-first layout:
   `[theme]` is never resolved or shown here.
 - `Settings > Notifications` owns notification delivery IA. Desktop notification
   mode, AI desktop notification dedupe duration, delivery source diagnostics,
-  AI hook quiet policy, in-app queue status, and
-  `PROJMUX_NOTIFY_HOOK` visibility live together without mixing mutation
-  boundaries.
+  and AI hook quiet policy live together without mixing mutation boundaries.
+  The in-app queue is consumed from the statusbar/sidebar, not from a standalone
+  Settings row. `PROJMUX_NOTIFY_HOOK` override presence is folded into Delivery
+  sources summary/detail instead of appearing as a separate root row.
 - `Settings > Notifications > Desktop notifications` owns the desktop
   notification mode. The detail choices are `none`, `notify`, and `raise`.
 - `Settings > Notifications > AI notification dedupe` owns the duplicate
@@ -67,10 +72,10 @@ view-first layout:
   the effective source; `PROJMUX_TMUX_NOTIFY_DEDUPE_SECONDS` remains the top
   override. The tmux bell fallback keeps its fixed 5 second window.
 - `Settings > Notifications > Delivery sources` shows Codex hooks, Claude, and
-  tmux producer diagnostics plus copyable install/remove/dry-run commands.
-  Settings copies command text only; it does not install or remove external
-  notify wiring. The legacy Codex notify source is intentionally omitted from
-  Settings.
+  tmux producer diagnostics, the effective desktop sender override state, and
+  copyable install/remove/dry-run commands. Settings copies command text only;
+  it does not install or remove external notify wiring. The legacy Codex notify
+  source is intentionally omitted from Settings.
 - `Settings > Notifications > Hook quiet policy` shows Codex/Claude hook
   runtime action values and writes only
   `${XDG_CONFIG_HOME:-$HOME/.config}/projmux/ai-hook-actions.json`. It does not
@@ -78,13 +83,17 @@ view-first layout:
 - `Settings > Session State > Sidebar startup picker` controls the Alt-1
   project-open startup selector. The saved file remains
   `${XDG_CONFIG_HOME:-$HOME/.config}/projmux/sidebar-startup-picker`.
-- `Settings > Labs` keeps experimental toggles, but keybindings no longer have a
-  visible Labs row. The hidden compatibility action redirects to the
-  `Settings > Keybindings` action list, not to a diagnostic default.
+- `Settings > Labs` contains only Live system resources and Project Hooks.
+  Keybindings live at `Settings > Keybindings`; Labs has no visible or hidden
+  keybindings redirect. Native is the only picker backend, so Labs does not
+  render picker source/backend information.
 - `Settings > Labs > Live system resources` is a direct global on/off toggle
-  for the Linux/WSL lower-status-row `CPU N%  MEM N%` segment. It defaults off,
-  updates live tmux state when toggled, and renders unavailable on unsupported
-  platforms. WSL copy identifies the values as the Linux guest/VM view.
+  for the macOS/Linux/WSL lower-status-row `CPU N%  MEM N%` segment. It defaults
+  off, updates live tmux state when toggled, and renders unavailable on
+  unsupported platforms. CPU and memory use fixed independent semantic
+  thresholds (CPU warning/critical at 70/90; memory at 75/90); the toggle does
+  not expose threshold customization. WSL values describe the Linux guest/VM
+  view.
 - `Settings > Labs > Project Hooks` is overview-first. The Labs root opens the
   overview, and the on/off mutation rows live one level deeper.
 - `Settings > AI Settings` is view-first. The root contains `Default split
@@ -106,6 +115,37 @@ view-first layout:
   `ko-KR`. When `auto` is active it must show the detected source (`LC_ALL`,
   `LC_MESSAGES`, `LANG`, or fallback). Unsupported locale tags must remain
   visible as warnings and fall back to `en-US`.
+- Global root descriptions keep ownership explicit: Appearance owns language,
+  AI badge style, and status/notification icon decoration; Theme owns presets,
+  color tokens, and font hints. About describes only the surface it retains.
+- `Settings > About` is intentionally compact: Version, Source, update
+  status/actions (including Latest, Update state, Installer, and Release notes
+  when available), Welcome, and Quit. It does not reproduce static key,
+  terminal, dependency, terminal-emulator, or documentation guides. Key
+  delivery discovery lives in `projmux setup`, supported terminal remediation
+  in `projmux setup terminal`, read-only dependency/runtime diagnostics in
+  `projmux doctor`, and broader orientation in Welcome and maintained docs.
+- Without an actionable project context, the Project surface renders one
+  passive context-guidance row instead of repeating the same disabled reason
+  for Trust, Hooks, Project recipe, and Effective merge view. With project
+  context, those four rows and Session State retain their existing actions.
+
+Settings mutation feedback follows one transient contract. The next picker
+frame inserts one passive `Feedback` row after Back; the row uses the catalogued
+`settingsNoopValue`, so Enter cannot create an unknown action. Selecting another
+navigation/action clears the old row before that operation runs, and a handled
+result replaces it. The inventory includes AI defaults/enabled agents/resume
+limits, notification modes/dedupe/hook policy, Appearance and locale choices,
+Labs toggles, project roots/workdirs/pins, project hooks/recipe/trust, Theme,
+Session State, direct keybinding reset/remove/toggle operations, and About
+update apply/check. Typed validation and staged apply failures stay in the
+popup instead of being visible only on stdout/stderr.
+
+The generic feedback inventory deliberately excludes Welcome, Quit,
+read-only hook/effective/notification diagnostics, Session State preview, and
+key capture/probe/diagnostic bodies. Those flows own a viewer, confirmation, or
+multi-step output surface; only an actual Settings write at their boundary is
+eligible for transient mutation feedback.
 
 Hooks remain the reference pattern for this IA:
 

package/docs/statusbar.md

@@ -69,10 +69,19 @@ row 1  [#S]  #{pane_current_path}  ⎈ <ctx>/<ns>  <git>  CPU 12%  MEM 41%  
   and tab titles are centered in a fixed-width trim so long active pane names
   do not resize the status row.
 - `Settings > Labs > Live system resources` adds the compact `CPU N%  MEM N%`
-  segment between git and the clock on Linux and WSL. It is global, default
-  off, and updates with tmux's existing five-second status interval. CPU is the
-  aggregate delta from `/proc/stat`; memory is
-  `(MemTotal - MemAvailable) / MemTotal` from `/proc/meminfo`. The first CPU
+  segment between git and the clock on macOS, Linux, and WSL. It is global,
+  default off, and updates with tmux's existing five-second status interval.
+  CPU and memory are host-scoped telemetry, not pane, window, project, or
+  session attribution. Each value has an independent semantic style: CPU is
+  normal below 70%, warning at 70–89%, and critical at 90% or above; memory is
+  normal below 75%, warning at 75–89%, and critical at 90% or above. Normal and
+  unavailable (`--`) values use the secondary status-text role, warnings use
+  the warning role, and critical values use the bold critical role. Styling one
+  value never promotes the other value.
+  Linux CPU is the aggregate delta from `/proc/stat`; memory is
+  `(MemTotal - MemAvailable) / MemTotal` from `/proc/meminfo`. macOS CPU uses
+  the aggregate Mach host tick delta; memory is total physical memory minus
+  free and inactive pages. The first CPU
   sample renders `CPU --%` until a second counter sample exists. WSL values are
   the Linux guest/VM view, not whole-Windows host utilization. The generated
   tmux condition prevents the status subprocess from running while the Lab is
@@ -80,6 +89,10 @@ row 1  [#S]  #{pane_current_path}  ⎈ <ctx>/<ns>  <git>  CPU 12%  MEM 41%  
   re-enabling after a pause starts at `CPU --%` instead of showing a long-term
   average. Missing or malformed procfs data degrades to `--` or an empty segment
   without producing a tmux error popup.
+  The complete live segment is wrapped in `#[range=user|resources]...#[norange]`.
+  Clicking it opens the same canonical client-scoped `resource-inspector`
+  popup as the `Resources:Open` keybinding action. Disabling the Lab hides only
+  the segment; it does not disable a custom action or `projmux resources`.
 - The settings chip keeps its label padding inside the `settings` range
   and inside the chip background. The compact app chip renders `` with
   the extra right-side icon padding painted by the same background, while
@@ -110,6 +123,7 @@ bind-key -n MouseDown1Status if-shell -F "#{==:#{mouse_status_range},window}" \
 | `kube`    | 0 | `projmux tmux popup-toggle sessionizer`   | `prefix s k`  |
 | `git`     | 0 | `projmux tmux popup-toggle sessionizer`   | `prefix s g`  |
 | `settings` | 0 | `projmux tmux popup-toggle --client <tty> ai-split-settings` | mouse only; `prefix s s` remains `session` |
+| `resources` | 0 | `projmux tmux popup-toggle --client <tty> resource-inspector` | mouse or custom `Resources:Open`; no default key |
 | `usage`   | 1 | show a native-framed usage HUD popup from cached usage state | `prefix s u`  |
 | `notify`  | 1 | `projmux focus --target <newest> --source status-bar --kind segment-click [--client <tty>]`, then ack on focus success | `prefix s n`  |
 
@@ -134,10 +148,14 @@ hard-truncate path still closes with `#[default]` so later status segments do
 not inherit notification styling. That dotless narrow fallback applies only to
 the queued notify segment, not to the separate window-list live attention badge.
 `usage` opens a native-framed detail HUD for the compact usage bar. It reads
-the cached usage state in-process, keeps the existing `projmux usage` CLI
-output shape unchanged for external consumers, aligns model/window rows with
+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
+`5h`/`weekly` cadence.
 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.

package/docs/testing.md

@@ -77,7 +77,7 @@ Observe:
 - `Alt-1` through `Alt-5` report `OK plain`. These are the guaranteed
   zero-config launch defaults.
 - If a guaranteed key reports `MISS timeout`, preview a supported terminal
-  mapping with `projmux init ghostty` or `projmux init windows-terminal`,
+  mapping with `projmux setup terminal ghostty` or `projmux setup terminal windows-terminal`,
   apply it with the same command plus `--apply`, restart that terminal if
   required, and rerun `projmux setup --timeout 10s`.
 - Optional direct aliases and transport-dependent chords may be reported by