From 11c573ea03892bb9111a008fe17a04a8ebfc8e50 Mon Sep 17 00:00:00 2001 From: "pulse-triage[bot]" <249995291+pulse-triage[bot]@users.noreply.github.com> Date: Sat, 5 Sep 2026 02:29:06 +0100 Subject: [PATCH] docs(web): distinguish refresh qualification from CI gates Green aggregate checks do not prove the standalone backup runners executed, and the related integration spec is non-gating probation coverage. Document the evidence boundary so release review does not mistake existing checks or retained samples for exact-revision refresh qualification. Change-source: pulse-maintainer --- frontend-modern/browser-tests/README.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/frontend-modern/browser-tests/README.md b/frontend-modern/browser-tests/README.md index 91101484b..8f5701af1 100644 --- a/frontend-modern/browser-tests/README.md +++ b/frontend-modern/browser-tests/README.md @@ -55,3 +55,21 @@ Narrow-width interaction is keyboard-driven, not touch or Brave qualification. The test does not cover Settings Manage editing, Authentication strategy selection, expansion padding, arbitrary inventory churn/reordering, or a deployed release. Passing is not grounds to close the mixed report #1869. + +## CI and release evidence + +These standalone runners are manual qualification commands: the current GitHub +workflows do not invoke them. A green Frontend or Core E2E check therefore does +not establish that either runner passed on the checked commit. Record the exact +source revision, command, viewport and output when using their results for +release review; retained JSON samples describe their recorded run, not later +commits or distributed images. + +The separate integration spec +`tests/integration/tests/64-workloads-proxmox-refresh-stability.spec.ts` covers +workload History, LXC refresh/deletion and off-screen PBS drawer scrolling. It is +currently listed in `PROBATION_SPECS` in `tests/integration/e2e-tiering.mjs`: +its failures are reported but do not fail the Core E2E gate. Inspect the probation +report as well as the aggregate check. It is not a substitute for these runners' +Coverage/By date assertions. Promotion remains subject to the existing ten-clean- +executed-main-runs rule; a local pass is not grounds to bypass it.