Initial setup becomes something the agent can run.
Added
references/scheduled-operation.md— scheduled execution was how the skill was actually operated, and nothing in the repository described it. The file states the contract an unattended run relies on (skill by name, corpus by absolute path, non-interactive push, a reachable messaging tool), gives recipes for an app scheduled task and for cron, and orders the diagnosis when the digest stops arriving: transcript, then corpus log, then the schedule itself.
Changed
references/setting-up-a-corpus.mdis now a runbook an agent can execute end-to-end, with the autonomy boundary stated first: the decisions only the user can make (interests, feeds, profile, destination, location) are collected in an explicit interview step, and everything after is mechanics. It also covers editing.newsrc.tomlitself, creating the private remote and verifying the visibility actually isPRIVATE, and a supervised--dry-runfirst run as the gate before scheduling.- The skill description and routing now name first-time setup and scheduling, so a setup request triggers the skill instead of stopping at "no corpus found".