feat(notify): reserve "page me" for desktop, "text me" for Signal

"page me" and "text me" now name distinct channels: page is the desktop notification, text is the Signal phone push, and "text and page me" fires both. Before, "page me" defaulted to desktop and the phone was an unnamed "on my phone" variant, so you couldn't name the phone without naming the machine.

I renamed the Signal tool agent-page to agent-text to match, with a deprecated agent-page shim delegating to it so callers and other machines don't break before their next install. The dispatch and tests are otherwise unchanged. I rewrote protocols.org "Reaching Craig", page-me.org, and work-the-backlog's away-run logic around the three phrasings, and updated the runbook.

1 files changed, 16 insertions, 8 deletions

diff --git a/.ai/workflows/page-me.org b/.ai/workflows/page-me.org
index bfa92c6..7a3b792 100644
--- a/.ai/workflows/page-me.org
+++ b/.ai/workflows/page-me.org
@@ -13,9 +13,17 @@ Uses the =notify= command (info type) for consistent notifications across all AI
 
 Craig says *"page me"* (or variations like "page me in 10 minutes", "page me at 3pm").
 
-The word "page" is the trigger for this workflow. It means: set a timed notification.
+The word "page" is the trigger for this workflow. It means: set a timed notification on the *desktop* channel (=notify=).
 
-Previously called "set-alarm" -- renamed to "page-me" for a distinctive, short trigger phrase that won't collide with common words like "remind" or "alert."
+Two sibling triggers pick a different channel; the timed =at= machinery below is identical for all three, only the fired command changes:
+
+- *"page me"* — desktop =notify= (this workflow's default).
+- *"text me"* — a Signal push to Craig's phone via =agent-text= (the away channel).
+- *"text and page me"* — both, for when he might be either place.
+
+Scope the triggers to the reflexive "me": "page me" and "text me", not a bare "page" or "text" in prose. The full channel vocabulary lives in protocols.org "Reaching Craig".
+
+"page" was chosen (renamed from the old "set-alarm") for a distinctive, short trigger that won't collide with common words like "remind" or "alert".
 
 * Problem We're Solving
 
@@ -113,18 +121,18 @@ notify info "Page" "Your message here" --persist
 
 The =--persist= flag keeps the notification on screen until manually dismissed. All page-me notifications should use =--persist= by default.
 
-** Paging Craig's phone (away from the machine)
+** Texting Craig's phone (the "text me" channel)
 
-The timed =notify= alarm above is the desktop channel. When Craig is away from the machine (or asks to be paged "on my phone"), use the agent pager instead — a Signal push to his phone from any machine or agent runtime:
+The timed =notify= alarm above is the desktop channel. When Craig says "text me" (or a run expects him away from the machine), use =agent-text= instead, a Signal push to his phone from any machine or agent runtime:
 
 #+begin_src bash
-agent-page "Build finished — ready for your eyes"
+agent-text "Build finished, ready for your eyes"
 
-# Timed phone page: same at-daemon pattern, different channel
-echo "agent-page 'Meeting starts in 5'" | at 3:25pm
+# Timed phone message: same at-daemon pattern, different channel
+echo "agent-text 'Meeting starts in 5'" | at 3:25pm
 #+end_src
 
-Channel selection and the pager's mechanics live in protocols.org "Paging Craig — the agent pager". When in doubt, fire both: the desktop notification persists for whenever he returns, the phone push reaches him now.
+Channel selection and the mechanics live in protocols.org "Reaching Craig". On "text and page me", fire both: the desktop notification persists for whenever he returns, the phone push reaches him now.
 
 ** Managing Alarms