README Weeding section and sample crontab line #328

Parent

#311

What to build

A README Weeding section beside "On a schedule". It covers one crontab line running thirdshift architect base main every few minutes (*/5) with merge.always, so that each Architect run starts as soon as the last one's plan is merged. It also says what pauses Weeding: a run still going, an open Architect plan (including one whose run failed), an Architect idea waiting for triage, a Ready issue. A skip exits 0 and sends no email, and the log shows why. thirdshift still never schedules itself (ADR 0009).

Give one sentence to the variant for repositories that also run a Pickup line: architect --plan-only on the Weeding line, with the Pickup run building the plan as an ordinary Ready issue, under the Claim limit. Add a Weeding line to the README's whole sample crontab, with a log folder of its own as the other commands have.

Acceptance criteria

• The README has a Weeding section with a copyable */5 crontab line using merge.always and the PATH and log conventions of "On a schedule".
• It lists every reason a Weeding pass is skipped, and says that skips send no email.
• It mentions the variant of --plan-only plus a Pickup line in one sentence.
• The whole sample crontab includes a Weeding line.
• Wording uses the glossary: Weeding, Architect run, Architect plan, Architect idea, Ready issue.

Blocked by

• A skipped Architect run sends no Run notification #325
• An Architect idea pauses Architect runs until it is triaged #326
• A Ready issue goes ahead of an Architect run #327