Hazard review

• scenarioreviewedboundaryerror_handlingmalformed_input

  Worst case: a route string carrying JSON-breaking bytes corrupts the payload and the shell rejects an otherwise valid verb - closed by jq -nc --arg encoding, which JSON-escapes the route unconditionally so any argv bytes arrive as a well-formed string payload; a route that is not a real menu id reaches the shell and surfaces as its own not-found handling on the plugin side. boundary: the case allowlist pins the five verbs plus help, with toggle/summon carrying payloads and close/refresh/ping the empty object - no verb/route combination builds a different call shape. error_handling is the declared class: exec replaces the process with omarchy-shell, so IPC failure surfaces as the client own exit status with no masking, retry, or swallow in this wrapper. Catalog 1.11.0 re-review: input_domain not applicable, it passes the route through as a JSON payload built by a JSON encoder. concurrency_scale not applicable, each CLI call execs one IPC call and keeps no state; the server side is stated on SW-REQ-260922-50RE.

• propertyreviewedtotality

  Every argv resolves to exactly one exec shape - five verbs with their fixed call forms, help with exit 0, unknown verb to the SNZG diagnostic arm - so the wrapper is total with no argument combination left undefined.

• structuralnot applicable

  jq --arg JSON encoding plus a case allowlist and exec; the route is never interpolated into a command string, only into a JSON payload field, and the verb never reaches a command name.

• domainnot applicable

  A local session-bus IPC call to the user own shell instance with user-chosen route data; no network, crypto, or privilege boundary, and no authority moves that the called plugin does not already hold.