[JacobStephens2]

Summary

0.6.0 ships the changes merged since v0.5.0. The headline is the Architect run (thirdshift architect [<focus>]): an Architecture review of the Base branch publishes its top recommendation as a plan, and thirdshift marks the plan ready and dispatches it as thirdshift <plan URL> would (#241). The other big change is that a Run now recognises an Inherited failure, a red check that is also red on the Base branch, and either fails at once or, when allowed, starts a Base fix (#226).

New command: thirdshift architect

• thirdshift architect [<focus>] --plan-only runs the Architecture review in a detached <repo>-architect worktree and reads the plan from its final line. It checks the plan, swaps needs-triage for ready-for-agent and prints the plan's URL. A failure after the review starts exits 1 and changes no label (thirdshift architect --plan-only: the Architecture review publishes a plan and thirdshift marks it ready #240).
• Without --plan-only, the Architect run goes on to the Spec run (a plan with sub-issues) or Run that thirdshift <plan URL> would start, and ends as that run does. It takes merge, no-merge and parallel <n>, with the User config's merge.always and spec.parallel as defaults; these flags are an argument error with --plan-only (Architect run dispatches its plan as a Spec run or a Run #244).
• When the review finds no Strong candidate, the Architect run exits 0 and prints the idea issue the review filed, or the open issue that already covers its top recommendation. No label is changed (Architect run with no Strong candidate: idea issue or already filed #243).
• The review uses four new headless Factory skills embedded in the binary: improve-codebase-architecture, to-spec, to-tickets and codebase-design (Headless Factory skills for the Architecture review #238).
• An Architect run asked for a Run notification, by email [address] or by email.always without no-email, sends exactly one however it ends. The run it dispatches sends none (One Run notification per Architect run #245).
• architect takes base-fix and no-base-fix, or the User config's base.fix, and hands them to the dispatched run. Both are rejected with --plan-only (Pass Base fix through an Architect run to its dispatched run #251).

Inherited failures and the Base fix

• A failed check that also failed on the Base branch commit the head last merged in is an Inherited failure. When every red check is one, the Run fails without a Repair: CI red on <check>, which also fails on <base> at <short sha>; fix <base> first. When the branch also has failures of its own, the CI-fix Repair gets only those, with the Inherited failures listed as not to fix (Inherited failures fail the Run without a Repair #225).
• With base-fix (or --base-fix), such a Run instead writes a Base fix issue labelled base-fix and ready-for-agent, adding either label if the repository lacks it. It starts a child Merge run into the Base branch, then merges the Base branch in and watches CI again. A Run gets one Base fix. On a Spec, a Ticket's Base fix goes into the Spec branch and the Spec PR's into the Base branch (A Base fix, when the base-fix flag is given #236).
• base.fix in the User config allows a Base fix for every Run, and no-base-fix forbids one for a single Run; giving both flags is an argument error. Setup asks about Base fixes only when every Run is a Merge run, and writes [base] fix = false otherwise (Base fix in the User config and Setup #239).
• One broken Base branch gets one Base fix: a Run that finds an open base-fix issue for the same Base branch and checks waits on it, with no time limit if it was written from another clone or machine. If the Base fix was started from the same Launch directory and has ended with its issue still open, the Run starts it again. Tickets of a Spec run that meet the same Inherited failure share one Base fix (Runs share one Base fix #242).
• A Run that took a Base fix ends its progress lines with Base fix: <issue URL> merged. A Ticket that landed after one says so in the Tickets checklist and the Spec run's Run notification (Inherited failures: fail fast on a red Base branch, or fix it with a Base fix #226).

Also: docs, test suite and release script updates (#209, #210, #213, #214, #215, #216, #217, #218, #220, #227, #235, #250).

Version diff

diff --git a/Cargo.lock b/Cargo.lock
index 901f597..6914e64 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1469,3 +1469,3 @@ dependencies = [
 name = "thirdshift"
-version = "0.5.0"
+version = "0.6.0"
 dependencies = [
diff --git a/Cargo.toml b/Cargo.toml
index 209a980..402114e 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -2,3 +2,3 @@
 name = "thirdshift"
-version = "0.5.0"
+version = "0.6.0"
 edition = "2024"