No error is a dead end: crash, click, and your agent is already looking

Claude-Session: https://claude.ai/code/session_01Ms2FbjQy31TVf3CEvQhGM8

tests/quickshell/notification-app-rules-contract

@@ -463,6 +463,20 @@ jq -e '. == {
     before: true, after: false, returned: true, soundAfterReturn: true, forgotUnknown: false
 }' <<<"$forgotten" >/dev/null || fail "forgetApp did not delete and restore a rule: $forgotten"
 
+# The command-as-data hint. A notification may name a shell command that the
+# CARD runs on a click, which is how a crash watcher that has already exited
+# still offers "diagnose this with your agent". Pinned here because the failure
+# mode is silent in both directions: a hint that stops being read turns every
+# rung of the escalation ladder into an ordinary notification, and an entry
+# that outlives its notification hands a later click a stale command.
+exec_hint="$(qs_for_test ipc call notification-app-rules-test execHint)"
+jq -e '. == {
+    plain: "",
+    carried: "panama-agent-crash 41283 kitty",
+    afterDismiss: ""
+}' <<<"$exec_hint" >/dev/null \
+    || fail "the panama-exec hint is not carried through the notification model: $exec_hint"
+
 # The urgency override is one answer, read by everything. The timeouts prove
 # the banner duration followed it and not only the colour.
 urgency="$(qs_for_test ipc call notification-app-rules-test urgency)"