Skip to content

README Weeding section and sample crontab line (#328) - #334

Merged
JacobStephens2 merged 2 commits into
issue-311from
issue-328
Oct 3, 2026
Merged

JacobStephens2 merged 2 commits into
issue-311from
issue-328

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Summary

README only: a Weeding section after "On a schedule", and a Weeding line in the whole sample crontab.

 ## Architect runs
   ### On a schedule
+  ### Weeding
+    */5 crontab line: thirdshift architect base main, with merge.always, log in commands/weeding/
+    skipped while: a run is still going · an Architect plan is open (one whose run failed included)
+                   · an Architect idea waits for triage · a Ready issue
+    a skip exits 0, sends no email, and leaves its line in the log
+    with a Pickup line: --plan-only, and the Pickup run builds the plan as a Ready issue under the Claim limit
 ## Pickup runs
   ### A Pickup run on a schedule
     whole crontab:
-      0 2 * * *    thirdshift architect base main              >> architect/cron.log
+      */5 * * * *  thirdshift architect base main --plan-only  >> weeding/cron.log
       */30 * * * * thirdshift pickup base main                 >> pickup/cron.log

The nightly Architect line in the whole crontab is replaced, not joined: a repository gets either a nightly Architect run or Weeding. The text says so and points back to the nightly line.

Evidence

  • Before: the README had no Weeding section. The whole crontab ran one Architect run a night.
    After: the Weeding section follows the code, and the review checked each claim: the skip reasons match src/main.rs and CONTEXT.md, and --plan-only labels the plan ready-for-agent (src/architect.rs). cargo test passes in full, command_surface included, which pins the README section names in the help text.

Merge Danger

Door: two-way

Blast Radius: docs

Unaddressed findings

Standards

  • The skip list repeats the reasons from "On a schedule" (possible Duplicated Code). Skipped: README Weeding section and sample crontab line #328 asks the Weeding section to list every reason a pass is skipped. Each bullet links to the section that owns the rule.

Spec

  • Suggest merge on the line instead of merge.always in the User config, so that only Weeding merges. Skipped: the spec asks for merge.always.

Closes #328

🤖 Generated with Claude Code

JacobStephens2 and others added 2 commits October 3, 2026 04:13
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…th merge.always, a plan whose run failed (#328)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JacobStephens2
JacobStephens2 merged commit ac468f2 into issue-311 Oct 3, 2026
13 checks passed
@JacobStephens2
JacobStephens2 deleted the issue-328 branch October 3, 2026 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant