docs: junit and pipeline-stage-view are live; record why it was never blocked

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

knowledge/hermes-automated-triage-24h-plan.md

@@ -1141,14 +1141,31 @@ Real homegrown service diagnoses (no action allowlisted, all escalated):
 - **Fixture storage**: the demo fixture is a ConfigMap, not a PVC. Longhorn
   attach latency and per-node engine availability made a PVC unreliable for
   a fast repeatable demo.
-- **JUnit evidence**: this Jenkins has no `junit` publisher and no
+- **JUnit evidence**: RESOLVED 2026-08-06. `junit 1369.v15da_00283f06` and
-  `pipeline-stage-view` plugin, so `testReport` and `wfapi` return 404 for
+  `pipeline-stage-view 2.41` are installed and active, with `scm-api` bumped
-  every job. `failed_tests` and `first_failed_stage` are therefore always
+  724 -> 728 as their `workflow-cps` requires. This was never actually blocked
-  empty. Console text is the only structured evidence, which drove the
+  on a core upgrade: only the *latest* `junit` (1418) needs core 2.533, while
-  failure-region extractor. Adding those two plugins (the current `junit`
+  1369 needs 2.504.3 and runs on 2.528.3. The earlier record was wrong because
-  release needs core 2.533; Jenkins here is 2.528.3, so a back-pin is
+  it read the plugin's latest release rather than the
-  required) is the largest remaining quality improvement and needs a
+  `dynamic-stable-2.528.3` update-center channel.
-  Jenkins restart — deliberately not done the night before a demo.
+
+  `testReport` and `wfapi` now return 200 where they returned 404 all night -
+  `ariadne` build 414 reports 1183 passing tests through the API. No Ariadne
+  change was needed: the evidence collector already fetched
+  `testReport/api/json` and had simply always received a 404, so
+  `failed_tests` now populates on its own.
+
+  This removes the *cause* of both diagnosis defects fixed the same day. With
+  no structured test data, console text was the only evidence, which is why
+  the enforced failure could be crowded out of the byte budget and why the
+  patcher could not locate a source file the console never named.
+
+  Cost: installing them required restarting the controller, which rescheduled
+  it onto a node without the image cached and produced a ~15 minute outage on
+  the image pull alone, plus three killed builds. Pre-pull the controller
+  image on the worker nodes before any future Jenkins restart; the agent image
+  had already been pre-pulled for exactly this reason and the lesson was not
+  carried across.
 - **Multibranch jobs are not detected**: folder-style jobs expose a null
   `lastBuild` at the job root.
 - **OpenSearch namespace** is still pinned to the demo namespace plus

services/comms/knowledge/hermes-automated-triage-24h-plan.md

@@ -1141,14 +1141,31 @@ Real homegrown service diagnoses (no action allowlisted, all escalated):
 - **Fixture storage**: the demo fixture is a ConfigMap, not a PVC. Longhorn
   attach latency and per-node engine availability made a PVC unreliable for
   a fast repeatable demo.
-- **JUnit evidence**: this Jenkins has no `junit` publisher and no
+- **JUnit evidence**: RESOLVED 2026-08-06. `junit 1369.v15da_00283f06` and
-  `pipeline-stage-view` plugin, so `testReport` and `wfapi` return 404 for
+  `pipeline-stage-view 2.41` are installed and active, with `scm-api` bumped
-  every job. `failed_tests` and `first_failed_stage` are therefore always
+  724 -> 728 as their `workflow-cps` requires. This was never actually blocked
-  empty. Console text is the only structured evidence, which drove the
+  on a core upgrade: only the *latest* `junit` (1418) needs core 2.533, while
-  failure-region extractor. Adding those two plugins (the current `junit`
+  1369 needs 2.504.3 and runs on 2.528.3. The earlier record was wrong because
-  release needs core 2.533; Jenkins here is 2.528.3, so a back-pin is
+  it read the plugin's latest release rather than the
-  required) is the largest remaining quality improvement and needs a
+  `dynamic-stable-2.528.3` update-center channel.
-  Jenkins restart — deliberately not done the night before a demo.
+
+  `testReport` and `wfapi` now return 200 where they returned 404 all night -
+  `ariadne` build 414 reports 1183 passing tests through the API. No Ariadne
+  change was needed: the evidence collector already fetched
+  `testReport/api/json` and had simply always received a 404, so
+  `failed_tests` now populates on its own.
+
+  This removes the *cause* of both diagnosis defects fixed the same day. With
+  no structured test data, console text was the only evidence, which is why
+  the enforced failure could be crowded out of the byte budget and why the
+  patcher could not locate a source file the console never named.
+
+  Cost: installing them required restarting the controller, which rescheduled
+  it onto a node without the image cached and produced a ~15 minute outage on
+  the image pull alone, plus three killed builds. Pre-pull the controller
+  image on the worker nodes before any future Jenkins restart; the agent image
+  had already been pre-pulled for exactly this reason and the lesson was not
+  carried across.
 - **Multibranch jobs are not detected**: folder-style jobs expose a null
   `lastBuild` at the job root.
 - **OpenSearch namespace** is still pinned to the demo namespace plus