From 13256aad033f84c0854f2d562685ea808a5ec619 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Fri, 12 Jun 2026 15:26:22 -0500 Subject: chore: delete the page-signal pager wrapper Remove the page-signal CLI wrapper, its workflow, and the references in INDEX.org, broadcast.org, and mcp/README.org. The signal MCP server stays. It's the two-way path and a separate capability. The pager number had deregistered and the send-only wrapper isn't worth re-registering. --- .ai/workflows/broadcast.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '.ai/workflows/broadcast.org') diff --git a/.ai/workflows/broadcast.org b/.ai/workflows/broadcast.org index 0d3d1c0..1be07d2 100644 --- a/.ai/workflows/broadcast.org +++ b/.ai/workflows/broadcast.org @@ -22,7 +22,7 @@ The mode picks the message template (Compose) and the receiving contract. Everyt - "let every project know X is available" Automatic announcement triggers: -- *New machine-global capability landed.* A new script in =~/.local/bin/=, a new MCP server, a new tool (e.g. =signal-cli=, =page-signal=). Projects need to know it's available. +- *New machine-global capability landed.* A new script in =~/.local/bin/=, a new MCP server, a new tool (e.g. =signal-cli=). Projects need to know it's available. - *Shared rule or protocol change* in =claude-rules/= or =claude-templates/.ai/= that materially changes how every project's agent should behave. - *Deprecation notice* — a script, workflow, or rule going away; give every project a chance to migrate. -- cgit v1.2.3