From 808a130141abd02b0767111f4344efda65329adc Mon Sep 17 00:00:00 2001 From: kokokoXUY <13682395396@163.com> Date: Sun, 27 Sep 2026 10:58:09 +0800 Subject: [PATCH] docs(dashboard): drop browser-smoke claims for the retired Ops view The Browser Smokes section described two smokes that protect the detailed `?view=ops` panel. That view is retired - the section already says the decision-freshness and promotion-readiness read models are covered by focused control-plane smokes instead of browser tests - and neither smoke exists any more: - `examples/dashboard-promotion-readiness-browser-smoke.mjs` is not in the tree; `examples/dashboard-browser-coverage.mjs` and the other `examples/dashboard-* browser-smoke.mjs` scripts do not include an ops-view smoke. - the decision-freshness coverage that remains is `examples/control_plane/decision-freshness-readmodel-smoke.py`, which reports a read model rather than rendered panel copy. The grouped-path sentence that follows (the demo-readiness group runs `examples/promotion-gate-smoke.py` before browser checks) is still true and is kept unchanged. Signed-off-by: kokokoXUY <13682395396@163.com> --- apps/presentation/dashboard/README.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/apps/presentation/dashboard/README.md b/apps/presentation/dashboard/README.md index 9806eb1e4b..4f5123e60f 100644 --- a/apps/presentation/dashboard/README.md +++ b/apps/presentation/dashboard/README.md @@ -452,18 +452,6 @@ usable. It uses an installed Playwright package or the Codex bundled runtime when available, and starts Vite through the local `vite` package rather than depending on `npm` / `npx` being on `PATH`. -The ops decision-freshness smoke protects the detailed `?view=ops` panel with -two public fixtures: a live-like zero-item summary and a stale/rebase-required -decision example. It verifies the rendered Chinese/English operator copy, -counts, top affected goal, and exact-replay wording instead of relying only on -source-string checks. - -The promotion-readiness smoke protects the detailed `?view=ops` panel with -fresh, stale, and missing readiness fixtures. It verifies the status badges, -readiness/rerun decision, artifact window, age, reason, and source-of-truth copy -for canary promotion readiness. The canonical fixture/browser script is -`examples/dashboard-promotion-readiness-browser-smoke.mjs`; use the npm script -above instead of calling ad hoc duplicate filenames. The grouped demo-readiness path also runs `examples/promotion-gate-smoke.py` before browser checks, so the structured `gate_state`, `can_promote`, and `should_warn` contract is covered even when browser smokes are skipped.