feat(workflows): generalize broadcast into announcement + situational modes

cross-project-broadcast handled tooling and rule announcements but had no shape for the situational case: a life or work event I want every project's agent to know, said once so none is missing context when I next talk to them. I renamed it to broadcast (helper and test alongside) and split it into two modes over the same fan-out plumbing. Announcement keeps the rigid capability template. Situational carries a general-not-comprehensive summary plus a fixed receiving-agent contract: record it in notes.org, hold it time-boxed or standing, apply on the project's own judgment, ask follow-ups at startup. The broadcasting agent does no per-project relevance analysis. Each receiving agent decides what the event means for its own work.

1 files changed, 3 insertions, 3 deletions

diff --git a/.ai/scripts/tests/test_cross_project_broadcast.py b/.ai/scripts/tests/test_broadcast.py
index 5919fbf..a0decf5 100644
--- a/.ai/scripts/tests/test_cross_project_broadcast.py
+++ b/.ai/scripts/tests/test_broadcast.py
@@ -1,4 +1,4 @@
-"""Tests for cross-project-broadcast.py: project fingerprinting + discovery.
+"""Tests for broadcast.py: project fingerprinting + discovery.
 
 Plain python3 script. The pure-ish helpers are driven against tmp project
 trees; discovery is exercised with SEARCH_ROOTS monkeypatched to the tree, and
@@ -11,12 +11,12 @@ from pathlib import Path
 
 import pytest
 
-SCRIPT = Path(__file__).resolve().parents[1] / "cross-project-broadcast.py"
+SCRIPT = Path(__file__).resolve().parents[1] / "broadcast.py"
 
 
 @pytest.fixture(scope="module")
 def bcast():
-    spec = importlib.util.spec_from_file_location("cross_project_broadcast", SCRIPT)
+    spec = importlib.util.spec_from_file_location("broadcast", SCRIPT)
     assert spec and spec.loader
     module = importlib.util.module_from_spec(spec)
     spec.loader.exec_module(module)