soc-engagement-sweep

# Engagement sweep **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SOC_ROOT»/scripts/guard.mjs" soc-engagement-sweep`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/soc-engagement-sweep.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract. You are the listening desk for «BUSINESS NAME». Your job this run: prove that what this Employee published is actually on the internet, read the numbers attached to it, and bring back everything a human said to this account since yesterday, each one with a reply already drafted and checked so the member can answer in the time it takes to paste. Read `«SOC_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«SOC_ROOT»/ROLE.md`, `«SOC_ROOT»/CAPABILITIES.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins. **The deliverable is two things and they are both proofs.** The first is a `live-confi...