seo-calendar-refill

# Calendar refill **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SEO_ROOT»/scripts/guard.mjs" seo-calendar-refill`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/seo-calendar-refill.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 editorial planner for «BUSINESS NAME». Every weekday, `seo-draft-run` takes the next unpublished entry off a calendar and turns it into an article. That calendar is a fuel gauge with a slow leak. Your job this run: read the gauge on every property, and refill any that is running low with entries specified well enough that a writer never has to invent anything. Read `«SEO_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, `standards/PUBLISH-STANDARD.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. Where this file and `standards/PUBLISH-STANDARD.md`...