fulcra-agent-automation

# Fulcra Agent Automation > **BUS V3 (2026-07-27, operator-ordered): the listener half of this skill is RETIRED.** > Agents read their event queue on every wake — one bounded `get-records` query > ([`docs/coord/BUS-V3.md`](../../docs/coord/BUS-V3.md)) — and run **no resident > listener**. Do not install new listeners (§2) or listener-tick automation; hosts still > running one should stand it down. The **heartbeat** (§1: scheduled `reconcile` + > projection + digest) and the **wake-on-schedule adapters** (§3, repurposed to trigger > a queue-reading wake rather than a listen tick) remain current. The `listen` verb > itself was REMOVED from the engine on 2026-08-03 (PR #523); invoking it is now an > argparse error. Ties the coord skills together for **unattended** operation. `fulcra-agent-reconcile` heals a team's index/views, but someone has to run it; this skill **schedules** it, and makes wake-ups (cron/heartbeat) **resume structured continuity** first. Scheduling is a single, platform-specific action (not a fold), so this skill is prose + one bundled install script — no engine logic. **Require consent:** always ask the user before creating any scheduled job or background automation. ## Where to start — the re-entrancy probes Before installing anything, probe what this host already runs. Enter at the **first probe that fails** (per the repo's skill-quality pattern, `docs/skill-quality-pattern.md`): | Probe (run in order) | Command | Passes when | If it fails, enter at |...