Require visual verification for aesthetic changes

This commit is contained in:
2026-09-04 19:44:25 -07:00
parent ad9f450343
commit 5c761b079d
2 changed files with 5 additions and 1 deletions
+4
View File
@@ -16,6 +16,10 @@ SQLite does not support adding a `NOT NULL` column without a default value to an
Do NOT add ad-hoc `ALTER TABLE` statements to `database.py` — that legacy list exists only to upgrade pre-Alembic databases to the baseline and must not grow.
## Visual verification
Always visually verify fixes or changes expected to have an aesthetic impact in the running app before marking them complete. Inspect browser screenshots of the affected UI, including relevant interaction states (such as expanded and collapsed panels) and screen sizes when layout is affected. Code review, DOM inspection, automated tests, and a successful build do not replace visual verification. Correct any visual issues found and inspect the result again. If visual verification is blocked, explicitly report the blocker and do not claim the appearance is verified.
## Learning during testing
When you run into a repeatable problem during testing (e.g. port assignment collision, missing executable, etc), note down the problem and solution in this file so that you'll have access to it in future sessions.