agents: require manual GUI testing, no automated screenshot-driving

Automating GUI verification (screenshot tools, simulated input) is unreliable and can prompt intrusive OS-level permission dialogs. GUI changes should be handed to the developer to run and visually inspect instead.
2026-07-06 20:12:35 -07:00
parent a59b9530bd
commit 0b2626b447
1 changed files with 4 additions and 0 deletions
@@ -67,3 +67,7 @@ wire protocols, key derivation salts, and CLI interfaces are all acceptable.
 - Use as many individual commits as necessary to implement a feature
 - This makes code review easier and enables cleaner git history/bisection
 - remember that jujutsu requires running 'jj new' to create a new commit on top of current work; without this unrelated changes might end up affecting the same commit
+
+# Testing
+- when developing GUI functionality, always ask the developer to manually run the GUI and visually inspect the output; do not try to automatically
+test GUI functionality using screenshots or other similar tools