feat(page-signal): route pages through a dedicated Signal pager account

Paging never actually reached the phone before. signal-cli was registered as my primary number, so a page was that account messaging itself, and Signal mobile doesn't push-notify a self-message. I registered signal-cli with a separate Google Voice number (profile "Claude Pager") and pointed everything at it. page-signal now sends from that account to my Signal account by default, so a page lands as a normal third-party message and rings the phone.

The old --note-to-self default is gone, since note-to-self on the pager account wouldn't reach me. Sender and default recipient now come from PAGE_SIGNAL_ACCOUNT and PAGE_SIGNAL_TO with baked-in defaults. The send command pins the sender with -a, and --to also accepts a Signal account UUID, since my account hides its phone number. servers.json points signal-mcp at the new number. Verified end-to-end: live sends from the pager account notified the phone, and signal-mcp shows connected.

1 files changed, 2 insertions, 2 deletions

diff --git a/.ai/workflows/page-signal.org b/.ai/workflows/page-signal.org
index a772603..e5d192f 100644
--- a/.ai/workflows/page-signal.org
+++ b/.ai/workflows/page-signal.org
@@ -6,9 +6,9 @@
 
 Send Craig a Signal message via =page-signal= when desktop notifications won't reach him. Signal fires cross-device, so a page arrives on his phone even when he's away from the desk. The wrapper lives at =~/.local/bin/page-signal= (rulesets-installed; symlinked from =claude-templates/bin/page-signal=).
 
-Defaults to =--note-to-self= for safety. Outbound (paging another contact) requires an explicit =--to <+number>= every call. No defaults, no batch.
+Pages Craig's Signal account by default, sent from a dedicated pager account. Override the recipient with =--to <+number-or-uuid>=. The sender account and default recipient come from =PAGE_SIGNAL_ACCOUNT= and =PAGE_SIGNAL_TO=, both with built-in defaults baked into the wrapper.
 
-*Known limitation (2026-05-29):* =signal-cli= is currently registered with Craig's primary number, so messages from it appear as "you sending from a linked device" rather than as an incoming message from a third party. Signal's mobile clients do not fire push notifications for these. Pages land in the conversation but don't ring the phone. The fix is to register =signal-cli= with a separate number (Craig's Google Voice number is the pending plan, see todo.org TODO scheduled 2026-05-29). Until that registration lands, this workflow is best used for *desktop-visible* paging (the notify wrapper, status outputs) rather than for reaching Craig cross-device. The wrapper itself works correctly; only the notification routing is awaiting the second-account registration.
+*Notification routing (resolved 2026-06-02):* =signal-cli= is registered with a dedicated Google Voice number (profile "Claude Pager"), separate from Craig's primary Signal account. A page travels from that account to Craig's Signal account, so it arrives as a normal incoming message from a third party and fires a mobile push notification. The earlier limitation — a primary-number account messaging itself, which Signal mobile won't notify on — no longer applies now that the sender is a distinct account. The literal sender number and default recipient (Craig's Signal account UUID) live in =page-signal= and =mcp/servers.json=.
 
 * When to Use This Workflow