refactor(cli-registry): make CLI backends data instead of per-mode branching

Every run mode is now a `CliEntry` in `src/config/cli-registry/` — discovery
(search dirs, version + identity probes), the launch argv template, env
handling, the `capabilities` flags that replace per-CLI branching, and the
`overlays` that back the remote/docker pane commands. Code that used to ask
"which CLI is this?" reads the entry instead.

Behaviour is unchanged. `test/cli-registry-spawn-golden.test.ts` pins every
spawn command as a literal string, captured from the hand-written builders
before they were deleted, and `test/location-overlay-commands.test.ts` does the
same for all 20 remote and in-container pane commands.

Config can never contain shell text: an entry declares typed argv tokens,
literals are validated against a safe-word pattern at LOAD time (a bad literal
rejects the whole entry — a silently dropped `--no-approve` is not cosmetic),
and values resolve through patterns NAMED in code, so a user `clis.json` cannot
widen its own validation. `~/.codeman/clis.json` overrides any entry, read-only
in this release.

OMP is included as a registry entry rather than a tenth hand-written builder,
so `buildOmpCommand()`, the omp availability pre-flight, the omp arm of
`buildPathExport()` and the omp entries in the truecolor/NO_COLOR, alt-screen
and doctor ladders all drop out.

Guard rails:

- `test/cli-registry-no-id-branching.test.ts` fails the build if per-CLI-id
  branching reappears outside `stock.ts`, in any of its four shapes (`===`,
  `!==`, `switch`/`case`, `includes`) — an `===`-only version would miss the
  negated forms, which is how 36 of them survived an earlier pass. Every
  allowlisted branch carries its reason.
- `external`, `hooks` and `altScreen` stay three INDEPENDENT capabilities;
  deriving one from another shipped the `until=stop`-hangs-on-shell bug.
- `param` is two namespaces. `launch.params` keys, `configSetenv.fromParam` and
  `privilegedParams[].param` all name a LAUNCH param; the legacy `<Mode>Config`
  wire field is separate, bridged only by `legacyConfigAliases`. Getting
  `privilegedParams[].param` wrong is SILENT — it is the multi-user bypass
  clamp's only handle on a CLI's privilege switch, and a wrong name clamps
  nothing with no error and no failing test — so `schema.ts` rejects an entry
  naming a param it never declared.
- Registry data resolves AT CALL TIME (`sessionModeSchema()`,
  `allowedEnvPrefixes()`, `dependencyRegistry()`, the resolvers' `searchDirs`
  thunks). A module-level const freezes at first import, so a CLI enabled while
  the server ran moved the run menu but not that surface.
- Six fields are annotated DECLARED-FOR-LATER and read by nothing
  (`shortBadge`, `accent`, `capabilities.echo`/`wheelForward`/
  `keyboardAccessory`/`maxFrameBytes`): all frontend behaviour, transcribed
  rather than measured. A test pins the list so it cannot quietly grow.

Three user-visible changes, all deliberate and named:

- `probeDockerCliVersion()` derives the in-container binary from the registry
  rather than assuming it equals the mode name (`antigravity` runs `agy`).
- The remote CLI version probe now covers grok and deepseek, which the
  hardcoded map it replaces omitted while its own comment said the rule was
  "every mode except shell".
- `codeman doctor`'s CLI rows are generated from the entries, so Claude's
  install hint is the install command rather than a docs URL, five CLIs gain
  hints they never had, and the row order follows the catalog.

Also hardened along the way: `sessionModeSchema()` is bounded at 24 chars
(matching the `cliId` pattern) before its failure message quotes the value
back, and `deepMerge` skips `__proto__`/`constructor`/`prototype` when reading
the hand-editable `clis.json`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WQkoi1cNegqVwZHgzx5SbJ

src/web/session-wait-registry.ts

@@ -65,6 +65,7 @@ import {
   MAX_SNIPPET_CONTEXT,
 } from '../config/agent-wait.js';
 import type { SessionMode, SessionStatus } from '../types.js';
+import { getCli } from '../config/cli-registry/registry.js';
 
 // ─── Signals ─────────────────────────────────────────────────────────────────
 
@@ -174,7 +175,7 @@ const HOOK_ONLY_SIGNALS: readonly WaitSignal[] = ['stop', 'blocked'];
 export interface HookCapabilityOptions {
   /**
    * `deepSeekConfig.statusReporting`, verbatim (so `undefined` means "not sent",
-   * i.e. ON). `false` is the per-session opt-out that stops `_configureDeepSeek()`
+   * i.e. ON). `false` is the per-session opt-out that stops `_configureCliEnv()`
    * exporting the `HERDR_*` triple, which is the ONLY thing that makes a dsh
    * session emit hook events at all.
    */
@@ -223,18 +224,26 @@ export interface HookCapabilityOptions {
  * function only about hook SIGNALS.
  */
 export function hooksAvailableForMode(mode: SessionMode, options: HookCapabilityOptions = {}): boolean {
-  if (mode === 'claude') return true;
-  // `deepseek` earns this the same way `claude` does — by emitting DEFINITIVE
-  // signals rather than having them inferred. The DeepSeek Harness terminal
-  // front door reports idle/working/blocked to its supervisor, and Codeman is
-  // that supervisor (see deepseek-status-shim.ts), so a dsh session really can
-  // deliver `stop` and `blocked` — unless the user turned the bridge off, in
-  // which case nothing on the box will ever post one. Every other mode is
-  // output-stabilization guesswork and must keep failing the ask.
-  if (mode === 'deepseek') {
-    return options.deepSeekStatusReporting !== false && options.deepSeekBridgeUnreachable !== true;
+  // A TRI-state capability, not a boolean, because the three answers are genuinely
+  // different questions — see CliCapabilities.hooks.
+  switch (getCli(mode)?.capabilities.hooks) {
+    case 'always':
+      // The CLI installs Codeman's own hooks block into its workspace (claude), so the
+      // signals are unconditional.
+      return true;
+    case 'supervised':
+      // The CLI REPORTS its own state to a supervisor and Codeman is that supervisor
+      // (deepseek, via deepseek-status-shim.ts) — definitive signals rather than inferred
+      // ones, which is what earns it a yes. But the user can disarm the bridge, and a
+      // docker/remote session cannot reach it at all; in either case nothing on the box
+      // will ever post one, so the answer has to come from the SESSION, not the mode.
+      return options.deepSeekStatusReporting !== false && options.deepSeekBridgeUnreachable !== true;
+    default:
+      // 'none', and an unregistered mode. Every other CLI's idle is output-stabilization
+      // guesswork, and must keep failing the ask rather than promising a signal that never
+      // arrives.
+      return false;
   }
-  return false;
 }
 
 /**