The runner docs do not mention the sweeper, write_log, lease_held or limit #70

Category: debt
Area: Docs (docs/RUNNERS.md, README.md)
Impact: Someone setting up a scheduler from the docs will not schedule reconcile-github-issues, and a runner that dispatches items itself will not know it must forward inputs.
Confidence: reproduced

Problem

After #50, #51 and #52 there is a new skill, new inputs and new result lines, and docs/RUNNERS.md does not mention any of them. Its Cadence section lists only the five steps, so a schedule built from it has no sweeper, and triage-github-issues calls reconcile-github-issues itself, so the two overlap unless the reader is told. The Inputs section sends the reader to the skills' own tables.

Cost of leaving it

Stale lease labels and finished issues are only tidied when triage-github-issues runs. A runner that starts its own sub-agents for items (as RUNNERS.md allows) will not know that the protocol now requires it to pass write_log=false and the group's inputs, so items log twice and lose runner and trusted_authors.

Where

docs/RUNNERS.md (Cadence, What a runner needs, Prompts), README.md (the step list), the generated skills/meta/runner-prompts/references/prompts.md (check the sweeper prompt reads well).

Done when

RUNNERS.md says when to schedule reconcile-github-issues (and that it also runs inside Triaging), what a runner that dispatches items must pass, and where the new inputs are defined. A reader can set up a schedule from it without opening the protocol.

Suggested direction

Keep it short. Link to Dispatching in the protocol instead of restating it.