[JacobStephens2]

Summary

0.7.0 ships the changes merged since v0.6.0. The headline is the Pickup run (thirdshift pickup, #292): one pass, with no Issue URL, that takes the lowest-numbered Ready issue and dispatches it as thirdshift <Issue URL> would. With it comes an Architect run that is safe to start from a timer (#257), so the operating system's scheduler can start both.

New commands

• thirdshift pickup [base <branch>] [merge|no-merge] [base-fix|no-base-fix] [parallel <n>] [email [<address>]|no-email] dispatches a Spec run if the issue taken has sub-issues, and a Run otherwise. A skipped pass exits 0 with stdout empty, one line of reason on stderr and no Run notification (Pickup runs: thirdshift takes ready-for-agent issues on its own #292, thirdshift pickup: take the lowest-numbered Ready issue and run it #293).
  • Ready issue rule: an open ready-for-agent issue with no Unready Ticket label, no Claim, no base-fix label and no open blocker, that is not a sub-issue, was never started, and was shaped at least 10 minutes ago. Each issue passed over gets one stderr line with the first reason that applies (thirdshift pickup: take the lowest-numbered Ready issue and run it #293, The rest of the Ready issue rule, and saying why an issue was passed over #296).
  • Sweep and Claim limit: before the search, a pass takes in-progress off closed issues. It is skipped when the open in-progress issues reach pickup.limit (default 3) in the User config (The Claim limit, and taking in-progress off closed issues #297).
  • Run notification: its checks come before any other work, and a pass that took an issue sends the one notification the dispatched Spec run or Run would have sent (One Run notification for a Pickup run that took an issue #298).
• thirdshift architect base <branch> (or --base <branch>) names the Base branch of an Architect run, so the branch checked out in the Launch directory stops mattering, and a detached HEAD is fine (thirdshift architect base <branch>: an Architect run names its Base branch #256).

New and changed behaviour

• The Claim: a Run or Spec run labels its issue in-progress in place of ready-for-agent, once its preflight checks pass and before its worktree is created. A Ticket's Run and a Base fix make no Claim (The Claim: a Run or Spec run marks its issue in-progress #291).
  • The Claim is removed after a merge that closed the issue, and kept when the run ends ready for review.
  • After a failure it is released, with the labels put back, only if the issue was never started: no Issue branch for it on origin and no pull request from one (Releasing a Claim, and removing it when thirdshift closes the issue #294, Pickup runs: thirdshift takes ready-for-agent issues on its own #292).
• One Architect run per repository at a time on a machine. One started while another is still running, its dispatched Spec run or Run included, is skipped: exit 0, one progress line, and a Run notification with skipped in its subject if asked. A killed run's leftover <repo>-architect worktree is removed first (One Architect run per repository at a time, with a skipped outcome #254). The lock is shared with a Pickup run, and the skip line now reads an Architect run or a Pickup run is already running on <owner>/<repo> (thirdshift pickup: take the lowest-numbered Ready issue and run it #293).
• One Architect plan at a time. Every Architect plan is labelled architect-plan, the label created if the repository lacks it. An Architect run is skipped while one is open, with each plan's URL on stdout and the command to pick it up (The architect-plan label, and skipping an Architect run while an Architect plan is open #264).
• Check re-run: a CI-fix Repair that leaves the head unchanged no longer fails the Run straight away. The failed GitHub Actions jobs get one re-run first, and the Run fails as a Declined CI fix only if that can't be done or a check of the branch's own is red again (Re-run failed checks once before a Declined CI fix fails the Run #267).
• Inherited failures: a Run that fails on them with no Base fix taken now links the failing checks on the Base branch. When nobody decided against a Base fix, it also offers a retry command with base-fix and the base.fix = true setting, on stderr and in the Run notification (Offer the Base fix, and link the failing checks, when an Inherited failure fails a Run #277).
• Child Runs: a Ticket's Run or a Base fix is started from the binary the parent is running, not its install path. On Linux, replacing or removing the installed thirdshift mid-run no longer stops later child Runs from starting (Start a child Run from the running binary, not its install path #265).
• Run endings: one module now owns how a Run's ending shows and how a child Run's is read back. What a Run prints does not change. A child's cause of several lines is now read back as its first line, and only the child's own progress lines can be its cause (One module for how a Run's ending shows and how a child Run's is read back #258).
• An Unready Ticket label now counts whatever its case, for a Spec run's Tickets and an Architect plan too (thirdshift pickup: take the lowest-numbered Ready issue and run it #293).

Also: README crontab recipes for an Architect run and a Pickup run with pointers in thirdshift help (#266, #299), the Pickup run glossary and ADR 0009 (#278), Day shift skills (#290), the pinned Rust toolchain (#273), and test and CI fixes (#268, #274, #276).

Version diff

diff --git a/Cargo.lock b/Cargo.lock
index 6914e64..fc7c32e 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1469,3 +1469,3 @@ dependencies = [
 name = "thirdshift"
-version = "0.6.0"
+version = "0.7.0"
 dependencies = [
diff --git a/Cargo.toml b/Cargo.toml
index 402114e..75442c9 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -2,3 +2,3 @@
 name = "thirdshift"
-version = "0.6.0"
+version = "0.7.0"
 edition = "2024"