docs(glossary): Add SIGINT and SIGQUIT terms, link from recipes

why: The interrupt recipe references SIGINT and SIGQUIT without
explaining them. Glossary terms with {term} cross-references let
readers hover or click for definitions.
what:
- Add SIGINT and SIGQUIT to docs/glossary.md with send_keys usage
- Link 4 occurrences in docs/recipes.md via {term} role

Author: tony

docs/glossary.md

@@ -33,4 +33,10 @@ Safety tier
 
 Socket
     The Unix socket used to communicate with a tmux server. Can be specified by name (`-L`) or path (`-S`).
+
+SIGINT
+    Interrupt signal (Ctrl-C). Sent via {ref}`send-keys` with `keys: "C-c"` and `enter: false`. Most processes terminate gracefully on SIGINT.
+
+SIGQUIT
+    Quit signal (Ctrl-\\). Sent via {ref}`send-keys` with `keys: "C-\\"` and `enter: false`. Stronger than {term}`SIGINT` — may produce a core dump on Unix. Use as an escalation when SIGINT is ignored.
 ```

docs/recipes.md

@@ -188,15 +188,15 @@ the target pane.
 
 ### Decide
 
-> Did the interrupt work? Some processes ignore SIGINT. I will wait briefly
+> Did the interrupt work? Some processes ignore {term}`SIGINT`. I will wait briefly
 > for a shell prompt to reappear. Developers use custom prompts, so I cannot
 > just look for `$`.
 
 The agent calls {tool}`wait-for-text` with `pattern: "[$#>%] *$"`,
 `regex: true`, and `timeout: 5`.
 
 > If the wait resolves, the shell is back. If it times out, the process
-> ignored Ctrl-C. I will escalate: try SIGQUIT (`C-\` with `enter: false`),
+> ignored Ctrl-C. I will escalate: try {term}`SIGQUIT` (`C-\` with `enter: false`),
 > then destroy and replace the pane only as a last resort.
 
 ### Act
@@ -214,9 +214,10 @@ submit a partially typed command, or enter a newline into a REPL.
 
 ### The non-obvious part
 
-Recovery is a two-step decision. Try the gentle approach first (Ctrl-C),
-verify it worked with {toolref}`wait-for-text`, escalate only if needed. The
-escalation ladder is: interrupt, verify, escalate signal, destroy. Skipping
+Recovery is a two-step decision. Try {term}`SIGINT` first (Ctrl-C),
+verify it worked with {toolref}`wait-for-text`, escalate to {term}`SIGQUIT`
+only if needed. The escalation ladder is: interrupt, verify, escalate signal,
+destroy. Skipping
 straight to {toolref}`kill-pane` loses the pane's scrollback history and any
 partially written output that might explain *why* it hung.