fix: route case-insensitive worker messages

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc

README.md

@@ -80,6 +80,12 @@ An operator or a worker can emit the same readable line:
 To:audit-core: Please review the authentication change.
 ```
 
+Protocol keywords are case-insensitive, so `to:`, `TO:`, `cmd:`, and their
+mixed-case forms work as well. Repository slugs remain exact. For full-screen
+terminal programs, tamq also recognizes `To:` immediately after a conservative
+worker-output gutter such as the `•` used to frame assistant output; operator
+prompt gutters are not worker output.
+
 Operator input is forwarded unchanged and is delivered with `/o`; a line
 originating in worker output has no suffix:
 
@@ -105,6 +111,8 @@ To:audit-core: please review the auth boundary
 ```
 
 The same line at the start of worker output queues a worker-originated message.
+The keyword may use any letter case, and a recognized full-screen output gutter
+may precede it.
 The `@`, `#`, reply shorthand, and interactive recipient composer from earlier
 alphas have been removed.
 
@@ -262,7 +270,8 @@ later phase.
 3. `tamq tap` is a full-duplex PTY proxy around every messaging-enabled shell
    or explicit command. It forwards bytes unchanged in raw terminal mode,
    propagates resize and lifecycle signals, observes operator input, and
-   normalizes worker output for start-of-line `To:` routing.
+   normalizes worker output for case-insensitive start-of-content `To:` routing,
+   including conservative full-screen worker-output gutters.
 
 This keeps tmux-specific topology concerns separate from reusable terminal I/O
 observation and message identity.