feat(pager): add agent-page, the runtime-neutral phone pager

The Signal pager reconcile found one pager identity, registered in velox's signal-cli, reachable from other machines only by hand-rolled ssh. agent-page wraps that: direct signal-cli on velox, ssh relay over the tailnet from everywhere else, a desktop-fallback hint when the relay fails, and the UUID target baked in so nobody pages the unregistered phone number again. Four bats tests stub ssh/uname/signal-cli to verify command construction; the real path was verified with a live phone push today. protocols.org's Paging Craig section now teaches both channels (notify for the desk, agent-page for the phone) and demotes signal-mcp to a velox-local nicety; page-me.org, work-the-backlog, and the INDEX carry the same two-channel story. Every project inherits on its next startup sync and make install.

1 files changed, 13 insertions, 0 deletions

diff --git a/.ai/workflows/page-me.org b/.ai/workflows/page-me.org
index dad5da6..bfa92c6 100644
--- a/.ai/workflows/page-me.org
+++ b/.ai/workflows/page-me.org
@@ -113,6 +113,19 @@ 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)
+
+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:
+
+#+begin_src bash
+agent-page "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
+#+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.
+
 ** Managing Alarms
 
 #+begin_src bash