docs require rendered visual evidence

Commit
ff183149a1c434e161aa6c1c71947ba990668ec6
Author
Marius Peter <dev@marius-peter.com>
Author date
Committer
Marius Peter <dev@marius-peter.com>
Committer date
.kiro/steering/workflow.md
index 722b02e6..8cf206e1 100644..100644
@@ -8,8 +8,10 @@
8 8 end-to-end tests for flows that cross module boundaries.
9 9 - Web tests check the affordances that let a user complete an action and the
10 10 user-visible result of that action.
11 Removed: - Do not test the DOM structure, CSS, layout, or styling. Review visual
12 Removed: changes with rendered evidence.
11 Added: - Do not test the DOM structure, CSS, layout, or styling. For a visual
12 Added: change, use Browser Mode and the web-verify skill to capture rendered
13 Added: evidence. If Browser Mode is unavailable, tell the user to turn it on.
14 Added: Do not report the change as complete before you capture the evidence.
13 15 2. The touched files are formatted with `ocamlformat --inplace`. Do not use
14 16 `dune fmt` (see Build directory safety).
15 17 3. The documentation agrees with the change.