fix(aw): require an explicit noop terminal state in agentic workflows

.github/workflows/canonical-pr-remediator.md

@@ -62,3 +62,22 @@ Return an in-depth remediation report that includes:
 - bounded patch plan (or explicit no-op)
 - test/check plan tied to the new head
 - why no unsafe action was taken
+
+## Terminal state contract
+
+Every run MUST finish by emitting at least one safe output. A run that emits
+nothing is not read as "healthy": the harness classifies it as `produced no
+safe outputs` and files a tracking issue, so silence produces noise instead of
+signal.
+
+When the correct outcome is to take no action -- healthy CI, unchanged state, a
+canceled or superseded run, or a preflight early exit -- call `noop` with a
+one-line reason instead of returning silently. `noop` is the explicit,
+deduplicated "nothing to do" record and is always the correct terminal state
+for a no-change run.
+
+Skip `noop` only when the run has already emitted some other safe output. Any
+safe output satisfies the requirement, including `missing_tool` and
+`missing_data` -- those are themselves valid terminal states, so a run that
+reports one is already accounted for and must not also emit `noop`. Never pair
+`noop` with another safe output in the same run.

.github/workflows/eventrelay-ci-investigator.md

@@ -83,10 +83,31 @@ Publish one deduplicated blocker update that includes:
 
 ## Behavioral constraints
 
-- Never create duplicate issues/comments for unchanged healthy state.
-- Exit before expensive analysis if preflight detects no state change.
+- Never create duplicate issues/comments for unchanged healthy state;
+  record that state with `noop` instead.
+- Exit before expensive analysis if preflight detects no state change, and
+  emit `noop` on that path rather than exiting silently.
 - Keep response report-first, deterministic, and SHA-bound.
 
+## Terminal state contract
+
+Every run MUST finish by emitting at least one safe output. A run that emits
+nothing is not read as "healthy": the harness classifies it as `produced no
+safe outputs` and files a tracking issue, so silence produces noise instead of
+signal.
+
+When the correct outcome is to take no action -- healthy CI, unchanged state, a
+canceled or superseded run, or a preflight early exit -- call `noop` with a
+one-line reason instead of returning silently. `noop` is the explicit,
+deduplicated "nothing to do" record and is always the correct terminal state
+for a no-change run.
+
+Skip `noop` only when the run has already emitted some other safe output. Any
+safe output satisfies the requirement, including `missing_tool` and
+`missing_data` -- those are themselves valid terminal states, so a run that
+reports one is already accounted for and must not also emit `noop`. Never pair
+`noop` with another safe output in the same run.
+
 ## Jules reporting requirement
 
 Return a detailed completion report with:

.github/workflows/focused-coverage-controller.md

@@ -85,3 +85,22 @@ Return an in-depth status report with:
 - exact failing or passing gate names
 - smallest next test-only increment
 - explicit stop reason if prerequisites are missing
+
+## Terminal state contract
+
+Every run MUST finish by emitting at least one safe output. A run that emits
+nothing is not read as "healthy": the harness classifies it as `produced no
+safe outputs` and files a tracking issue, so silence produces noise instead of
+signal.
+
+When the correct outcome is to take no action -- healthy CI, unchanged state, a
+canceled or superseded run, or a preflight early exit -- call `noop` with a
+one-line reason instead of returning silently. `noop` is the explicit,
+deduplicated "nothing to do" record and is always the correct terminal state
+for a no-change run.
+
+Skip `noop` only when the run has already emitted some other safe output. Any
+safe output satisfies the requirement, including `missing_tool` and
+`missing_data` -- those are themselves valid terminal states, so a run that
+reports one is already accounted for and must not also emit `noop`. Never pair
+`noop` with another safe output in the same run.