From 2d41e960a48bf039b6f3283764485a7e1edda8c2 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Fri, 27 Mar 2026 16:56:48 +0000 Subject: [PATCH] docs(governance): require Playwright for frontend changes --- docs/release-control/internal/AGENT_VALUES.md | 3 ++- docs/release-control/internal/CONTROL_PLANE.md | 6 ++++++ .../v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md | 4 +++- 3 files changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/release-control/internal/AGENT_VALUES.md b/docs/release-control/internal/AGENT_VALUES.md index 9affe9f0c..f6a6ed2c8 100644 --- a/docs/release-control/internal/AGENT_VALUES.md +++ b/docs/release-control/internal/AGENT_VALUES.md @@ -105,7 +105,8 @@ that already belong to the canonical system. 18. Treat browser truth as product truth for customer surfaces. Code-level proof matters, but customer-facing surfaces are not acceptable until real in-browser behavior and interaction quality are good enough to - deserve normal use. + deserve normal use. When a slice changes frontend code, inspect the changed + surface in Playwright before calling that slice progress or done. ## Delegation Rule diff --git a/docs/release-control/internal/CONTROL_PLANE.md b/docs/release-control/internal/CONTROL_PLANE.md index f2661a555..f2055ebc1 100644 --- a/docs/release-control/internal/CONTROL_PLANE.md +++ b/docs/release-control/internal/CONTROL_PLANE.md @@ -146,6 +146,12 @@ model that active and future release profiles reuse. untrustworthy in real browser use, the control plane should steer the agent toward redesigning the owning model or boundary instead of continuing narrow same-shape iteration on that weak baseline. +21. Frontend slices require browser proof at the browser layer. + For frontend or UI changes, a build and code-level tests are not enough to + call the slice progress. The changed surface must be exercised in + Playwright after the current build, and that browser inspection should + inform whether the slice is acceptable, still prototype-grade, or needs a + deeper redesign. ## Canonical Files diff --git a/docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md b/docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md index 9e720bd24..2a97d9ac4 100644 --- a/docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md +++ b/docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md @@ -267,7 +267,9 @@ Every substantial task must finish by checking these questions: For important customer-facing UI, code-level proof is not enough by itself. If the surface is meant to be trusted or used normally, exercise it in-browser and judge whether it actually deserves more iteration in its - current shape. + current shape. If the slice changed frontend code, inspect the changed + surface in Playwright after the current build before treating the work as + progress, improvement, or done. They are not the work item by themselves unless the remaining gap is explicitly governance-only. For ordinary lane work, identify the runtime, product, ownership, or