feat(freeze): SupervisionOutcome derives Clone/PartialEq/Eq + decision-record refinements (overall-review)

Author: ZelAnton

CHANGELOG.md

@@ -13,6 +13,9 @@ to a dated version section.
 
 ### Added
 
+- `SupervisionOutcome` now derives `Clone`, `PartialEq`, and `Eq` — consistent
+  with the other result types (`ProcessResult`, `Finished`, `Outcome`,
+  `RunProfile`), so a supervision report can be stored, compared, and logged.
 - `Outcome` gained accessor methods — `code() -> Option<i32>`,
   `signal() -> Option<i32>`, `timed_out() -> bool` — so code holding a bare
   `Outcome` (e.g. from `RunningProcess::wait` or `Finished::outcome`) needn't

decisions/interface-freeze-2026-06.md

@@ -46,6 +46,13 @@
   bound and accepts strictly more closures. Crucially this is the *freeze-safe*
   side: loosening a bound later is non-breaking, tightening is breaking — so the
   permissive state is the right one to lock.
+- **Keep the batch free-fn argument order `output_all(commands, concurrency,
+  runner)`** (and `output_all_bytes`). It reads "what to run, how many at once,
+  who runs them"; the three arguments are distinctly typed so a mis-order won't
+  compile, and the order has been stable across many releases. The runner trails a
+  scalar (unlike the receiver-style `runner.checked(..)`), but these are
+  free-function batch helpers with no receiver, so there is no convention to
+  violate. Frozen as-is.
 - **Keep `Copy` on the small scalar value types** (`Outcome`,
   `OutputBufferPolicy`, `ResourceLimits`, `ProcessGroupStats`, `RunProfile`, and
   the unit-ish enums). They are all-scalar; `Copy` is a real ergonomic and the
@@ -86,8 +93,14 @@
 - Features are additive; default set is `process-control` only; the `mock`
   expectation surface is semver-exempt and feature-gated. MSRV 1.88 / edition 2024.
 
+## Additive polish landed this round (not freeze-critical, done for day-one consistency)
+
+`SupervisionOutcome` now derives `Clone`/`PartialEq`/`Eq` (was `Debug`-only) — it
+was the lone result type without them. Additive, but shipped now so the result-type
+surface is uniform on release.
+
 ## Genuinely deferred (additive — safe to add after 1.0, not freeze-critical)
 
-`Clone`/`PartialEq` on `SupervisionOutcome`; builder methods on `ResourceLimits`;
-more crate-root free fns (`output_bytes` / `run_unit`); an `Outcome::signalled() ->
-bool` companion. All purely additive — no freeze pressure.
+Builder methods on `ResourceLimits`; more crate-root free fns (`output_bytes` /
+`run_unit`); an `Outcome::signalled() -> bool` companion. All purely additive — no
+freeze pressure.

public-api.txt

@@ -856,8 +856,14 @@ pub processkit::SupervisionOutcome::final_result: processkit::ProcessResult<allo
 pub processkit::SupervisionOutcome::restarts: u32
 pub processkit::SupervisionOutcome::stopped: processkit::StopReason
 pub processkit::SupervisionOutcome::storm_pauses: u32
+impl core::clone::Clone for processkit::SupervisionOutcome
+pub fn processkit::SupervisionOutcome::clone(&self) -> processkit::SupervisionOutcome
+impl core::cmp::Eq for processkit::SupervisionOutcome
+impl core::cmp::PartialEq for processkit::SupervisionOutcome
+pub fn processkit::SupervisionOutcome::eq(&self, &processkit::SupervisionOutcome) -> bool
 impl core::fmt::Debug for processkit::SupervisionOutcome
 pub fn processkit::SupervisionOutcome::fmt(&self, &mut core::fmt::Formatter<'_>) -> core::fmt::Result
+impl core::marker::StructuralPartialEq for processkit::SupervisionOutcome
 impl core::marker::Freeze for processkit::SupervisionOutcome
 impl core::marker::Send for processkit::SupervisionOutcome
 impl core::marker::Sync for processkit::SupervisionOutcome

src/supervisor.rs

@@ -81,7 +81,7 @@ pub enum StopReason {
 ///
 /// Non-exhaustive: a read-only report the crate produces — new telemetry can
 /// be added without a breaking change.
-#[derive(Debug)]
+#[derive(Debug, Clone, PartialEq, Eq)]
 #[non_exhaustive]
 pub struct SupervisionOutcome {
     /// The result of the final run (the one that ended supervision).