/wbBroadcast — Live Demo ()
This is what /wbBroadcast actually does on wb-labs as the workspace stands today (2026-05-05). The matrix below mirrors the exhaustive simulation, but every cell is filled from the live state of the repo.
1. Live target
| Field | Live value |
|---|---|
| Configured channels | #dev, #ops, #ci-notifications (Slack webhooks in .agents/config/) |
| Internal PubSub | 4 micro-frontends listening: demo.wbc-ui.com, md.wbc-ui.com, wbc-ui.com, wb-press2.wbc-ui.com |
| Last broadcast | wb-core v4.5.2 published (2026-05-03, to #dev) |
| Pending events | wb-core WBC.js decomposition completed → cache purge needed |
2. What each argument resolves to today
| Argument | Live resolution |
|---|---|
/wbBroadcast #dev -m="wb-core row 3 complete" | Sends text to #dev Slack channel. |
/wbBroadcast event:purge_cache -d='{"scope":"wb-core"}' | Fires internal PubSub event to 4 micro-frontends. |
/wbBroadcast #dev,#ops -m="Plan complete" | Multicast to both channels simultaneously. |
3. Pipelines on this exact workspace
/wbBroadcast Live Execution Simulator
Notify team after completing wb-core plan
/wbBroadcast #dev -m="wb-core plan complete: JWT handshake, renderString escape, WBC.js decomposition all done. Pending validation on row 3."> /wbBroadcast #dev -m="wb-core plan complete: JWT handshake, renderString escape, WBC.js decomposition all done. Pending validation on row 3."[SYSTEM] Single-channel broadcast to #dev.
[PAYLOAD] Text: "wb-core plan complete: JWT handshake, renderString escape, WBC.js decomposition all done. Pending validation on row 3."
[DISPATCH] #dev → 200 OK (0.3s)
[OK] Broadcast sent.
💠 Pipeline Notify team after completing wb-core plan
💠 Pipeline Cache purge after WBC.js decomposition
The WBC.js decomposition changed the export surface. Micro-frontends that import from wb-core need to drop their caches:
💠 Pipeline Dry-run before multicast
4. What would refuse today
| Trigger | Live response |
|---|---|
/wbBroadcast #dev (no message) | ❌ Empty payload. Use -m or -d. |
/wbBroadcast #unknown-channel -m="test" | ⚠️ Channel #unknown-channel not configured. Available: #dev, #ops, #ci-notifications. |
/wbBroadcast event:purge_cache (no -d) | Proceeds with empty data payload. Event fires with just the timestamp. Not a refusal — events can be signals without data. |
The pattern: /wbBroadcast is the workspace's outward voice. It tells external systems and internal consumers what happened. Fire-and-forget by design — a failed broadcast never blocks work.