From f4f4c5f3b8d9066eb521cf3e35234ce4a6bb7718 Mon Sep 17 00:00:00 2001 From: mkorwel Date: Sat, 14 Mar 2026 12:35:19 -0700 Subject: [PATCH] docs(cli): focus visual validation guide on exposure of issues --- docs/cli/visual-validation.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/cli/visual-validation.md b/docs/cli/visual-validation.md index 071730e67f..681cce0cb0 100644 --- a/docs/cli/visual-validation.md +++ b/docs/cli/visual-validation.md @@ -124,10 +124,11 @@ Existing testing layers often miss critical user experience regressions: that the resulting state (like a policy violation) is actually visible to the user. -The new validation tools bridge these gaps. For example, the Policy Engine was -previously "broken" not because of logic errors, but because visual feedback was -suppressed in certain modes and the scheduler was prone to TTY-based race -conditions. These tools caught both. +The new validation tools bridge these gaps. For example, they were used to +expose critical issues where visual feedback for the Policy Engine was +suppressed in certain modes and the core scheduler was prone to TTY-based race +conditions. The high-fidelity validation provided by these tools was essential +for identifying and verifying the fixes for these issues. ## Next steps