Take the website's screenshots with one command

composer screenshots runs Pest browser tests in tests/Screenshots, outside
every test suite: fixed demo data under a frozen clock, desktop (MacBook
14, 2x) and phone (iPhone 15 Pro, 3x) in light and dark, each capture
published at once as WebP at two widths into website/img/screenshots.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy

.ai/rules/index.md

@@ -7,3 +7,5 @@ Before planning or editing, find the row whose globs match the file's path and r
 | config/livewire-material.php | .ai/rules/config.md |
 | resources/css/material-scheme.* | .ai/rules/css.md |
 | resources/views/livewire/share-download.blade.php | .ai/rules/livewire.md |
+| tests/Screenshots/** | .ai/rules/screenshots.md |
+| website/** | .ai/rules/website.md |

.ai/rules/screenshots.md

@@ -0,0 +1,9 @@
+---
+paths:
+  - 'tests/Screenshots/**'
+---
+
+# Screenshots
+
+## Screenshots come from composer screenshots, before a release
+Run `composer screenshots` whenever the interface changes and before a release; it builds assets and runs tests/Screenshots (not part of any test suite or CI), publishing WebP files to website/img/screenshots. Demo data (DemoData) and the clock are fixed so runs are reproducible. Traps: Pest only starts its browser for a test whose body calls `visit(` after whitespace; Livewire's temporary-upload cleanup must stay off under the frozen clock or it deletes the selected files; the in-process server's random port is shown as https://files.example.com and the QR redrawn for it; upload_max_filesize/post_max_size are set to 4G by the script so the admin settings hint does not show the machine's PHP limit.