[JacobStephens2]

Summary

0.13.2 ships the changes merged since v0.13.1. The headline is that the Security review now runs on the User config's security.harness when it is set (#932). The review uses that Harness's own [harness.<name>] Model and Effort, in a Run, on a Spec run's Spec PR and in a Base fix. Every other session keeps the Command's Harness, and the command's harness, model and effort words don't move the review. When a review will run on the security Harness, that Harness is checked before any work, and the Run fails early if it can't run. New ADR-0021 says a Command may use more than one Harness.

• Failure reports now name the Session log of the session the failure's cause came from, rather than just the last session that ran (Report a failure with the Session log of the session its cause came from #933):
  • A Security hold reports the Security review's log, even after later Repairs.
  • A Spec run whose Tickets are not done reports the one failed Ticket's log, or none if several failed.
  • The terminal report, the Command log and the Run notification agree on which log they name.

Also: docs updates in #932 (glossary, guide, Setup and site docs).

Version diff

diff --git a/Cargo.lock b/Cargo.lock
index 196633e..644b2d2 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1737,3 +1737,3 @@ dependencies = [
 name = "thirdshift"
-version = "0.13.1"
+version = "0.13.2"
 dependencies = [
diff --git a/Cargo.toml b/Cargo.toml
index 8f787f8..3d3cfe8 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -2,3 +2,3 @@
 name = "thirdshift"
-version = "0.13.1"
+version = "0.13.2"
 edition = "2024"