From 8e6d00a57fe012acca862ea9790dee6176d4b842 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sun, 14 Jun 2026 17:33:33 +0200 Subject: [PATCH] docs(claude): require real UI/user-flow live validation (A4) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per the F9 storage episode — live validation of a user-facing feature must exercise the real flow end-to-end, not shortcut via direct API/agent/CLI calls. Low-level mechanism tests are exempt. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 8a362bb..9be0cf8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -96,6 +96,10 @@ All shippable work commits **directly to `main`**; `main` is always equal to wha - Code quality: verify generated code for bugs/edge cases; add debug logging; **ask rather than guess** when you'd otherwise invent input/output. +### Live validation + +Live validation of a user-facing feature must exercise the real UI/user flow end-to-end (e.g. connect → enroll → deploy), not shortcut via direct API/agent/CLI calls — a shortcut can give false confidence and leave the system inconsistent (see the F9 storage episode). Low-level mechanism tests where the direct call IS the mechanism are exempt. + ## Workflow & artifacts - Implement **`TASK.md` / `TASK-*.md`** specs (when placed as `TASK.md` or told to implement one), then push + CHANGELOG + REPORT.md.