diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-13 18:30:48 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-13 18:30:48 -0500 |
| commit | 49be354ff18d6739e478ee4f5ab46de6cb9e4f81 (patch) | |
| tree | 80bffd6f32c39c2f98a0cd8dea86aba766b8d43b /.ai/workflows/work-the-backlog.org | |
| parent | 0de6e09a4a6014270b0a8b77cfac7661b8cdf5dd (diff) | |
| download | rulesets-49be354ff18d6739e478ee4f5ab46de6cb9e4f81.tar.gz rulesets-49be354ff18d6739e478ee4f5ab46de6cb9e4f81.zip | |
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.
Diffstat (limited to '.ai/workflows/work-the-backlog.org')
| -rw-r--r-- | .ai/workflows/work-the-backlog.org | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.ai/workflows/work-the-backlog.org b/.ai/workflows/work-the-backlog.org index 462e6b2..090841d 100644 --- a/.ai/workflows/work-the-backlog.org +++ b/.ai/workflows/work-the-backlog.org @@ -152,7 +152,7 @@ With paging on, fire one page when the set is done or the cap is hit — end-of- notify info "Page" "<project>: <N> done, <M> remaining — <one-line summary>" --persist #+end_src -=--persist= keeps it on screen until dismissed, and =info= is the page-me urgency convention (persistent but never crash-scary). The page fires when the set completes *or* the cap stops the run — either way exactly once. The message carries the project name, the completed count, and the remaining count (with skipped tasks noted in the run summary) so Craig can confirm ready and name the next project in one reply. There is no separate page-signal call — =notify= is the paging surface. +=--persist= keeps it on screen until dismissed, and =info= is the page-me urgency convention (persistent but never crash-scary). The page fires when the set completes *or* the cap stops the run — either way exactly once. The message carries the project name, the completed count, and the remaining count (with skipped tasks noted in the run summary) so Craig can confirm ready and name the next project in one reply. =notify= is the desktop paging surface; a run that expects Craig to be away also fires =agent-page= with the same message (the Signal phone channel — protocols.org "Paging Craig — the agent pager"). * Metrics |