importance: mark an agent high, normal, or low

within a status, more important agents are listed first, and so jumped to
first; status stays first. a high agent shows a bold ! before its name, a
low agent's name is lightly dimmed with "low" on its second line, and it
makes no sound (it still notifies and waits in line).

in pi, /importance high|normal|low (completes the levels; none once one is
typed out, so Enter runs it). the extension saves it in the session as a
custom entry (dingger-importance), so /reload, restarts, /resume and
restore bring it back; /new starts at normal. it shows a level other than
normal in pi's footer, emits dingger:importance { level } for other
extensions, and sends it with every report. for other agents, `dingger
importance [level] [--pane]`; it refuses a pi that reports itself, whose
saved level would win.

the daemon stays the one writer of pane state: it writes
@dingger_importance (unset for normal), which goes with the agent and
survives a daemon restart. `dingger status` marks high and low.

tests: e2e step 21 (order, the option, no sound for low, the menu bar,
the command, the extension through a harness that now matches pi's
extension API), a DINGGER_SOUND seam so sounds are observable, and a
status-line check that read the counts once (flaky) now polls.
pi-live: /importance in real pi 1.4, its footer and session entry, and the
level after a restore; every pi there now uses the test's agent directory
(a restored pi read the user's). negative controls fail each part.

1 files changed, 20 insertions, 1 deletions

diff --git a/README.md b/README.md
index a0c4097..13a7b9c 100644
--- a/README.md
+++ b/README.md
@@ -94,6 +94,18 @@ than a poll is still a completion.
   skipping the window you already look at.
 - **Notifications**: "needs attention" (blocked) and "finished" (done), with
   herdr's sounds; silent for completions you are already watching.
+- **Importance**: mark an agent high, normal (the default), or low. Within a
+  status, more important agents are listed first, so a jump goes to them
+  first; status still comes first (a blocked low agent before a done high
+  one). A high agent shows a bold `!` before its name; a low agent's name is
+  lightly dimmed, its second line says "low", and it makes no sound (it
+  still notifies, and waits in line like any other). In pi, type
+  `/importance high|normal|low` (no argument: the current level); pi saves
+  it with the session, so it comes back after `/reload`, a restart, or a
+  restore, and its footer shows a level other than normal. For other agents,
+  run `dingger importance high|normal|low` in the agent's pane (in Claude
+  Code: `! dingger importance high`), or pass `--pane`; it lasts until the
+  agent exits.
 
 ## Where state comes from
 
@@ -108,7 +120,13 @@ than a poll is still a completion.
    manifests, for agents without hooks.
 
 All per-pane state lives in tmux pane options (`@agent_state`,
-`@dingger_since`, `@dingger_hook`), so restarting dingger loses nothing.
+`@dingger_since`, `@dingger_hook`, `@dingger_importance`), so restarting
+dingger loses nothing.
+
+The pi extension's reports carry the agent's importance. Other pi
+extensions can follow it on pi's event bus: `dingger:importance` with
+`{ level }`, at session start and on every change; it is saved in the
+session as a custom entry of type `dingger-importance`.
 
 ## Usage
 
@@ -116,6 +134,7 @@ All per-pane state lives in tmux pane options (`@agent_state`,
 dingger watch                 # the daemon (run by launchd, see below)
 dingger status                # agents in priority order
 dingger focus [--pane ID]     # jump to an agent (default: the top waiter)
+dingger importance [LEVEL]    # an agent's importance: high, normal, low
 dingger install pi            # install the pi state-reporting extension
 dingger install claude        # report Claude Code sessions, for restore
 dingger install zsh           # record typed command lines, for restore