Use sandbox screenshot uploader

Closes #17

Author: alexeygrigorev

.claude/agents/designer.md

@@ -33,6 +33,19 @@ Do not use this role for backend-only, queue, SES, SQS, Lambda, or data-model is
 4. Report hierarchy, spacing, typography, accessibility, and mobile issues.
 5. Provide concrete recommendations and file references.
 
+## Screenshot Uploads
+
+Save screenshots under `.tmp/` in the Datamailer checkout and upload them with the shared sandbox screenshot CLI:
+
+```bash
+cd /home/alexey/git/sandbox-screenshots
+upload-screenshot /home/alexey/git/datamailer/.tmp/screenshot.png
+```
+
+Read `/home/alexey/git/sandbox-screenshots/README.md` before uploading. If the CLI is missing or stale, run `./install.sh` from that repo and `source ~/.bashrc`.
+
+Include returned `url` values in the audit. Do not use an orphan `screenshots` branch. If a local or remote `screenshots` branch exists, delete it, reupload screenshots with `upload-screenshot`, and update affected issue comments.
+
 ## Output
 
 ```markdown

.claude/agents/tester.md

@@ -65,7 +65,14 @@ make test-aws-local
 
 If LocalStack is unavailable and the issue only requires skip-safe local setup, verify the marked tests skip cleanly and report that. If the issue requires a real local queue run, start LocalStack or fail with concrete instructions.
 
-For UI-visible changes, start the server, inspect the page, and capture/read screenshots when practical. For backend-only changes, state screenshots are not applicable.
+For UI-visible changes, start the server, inspect the page, and capture/read screenshots when practical. Save screenshots under `.tmp/` and upload shareable images with the sandbox screenshot CLI:
+
+```bash
+cd /home/alexey/git/sandbox-screenshots
+upload-screenshot /home/alexey/git/datamailer/.tmp/screenshot.png
+```
+
+Read `/home/alexey/git/sandbox-screenshots/README.md` before uploading. If the CLI is missing or stale, run `./install.sh` from that repo and `source ~/.bashrc`. Include the returned `url` values in the QA report. Do not use an orphan `screenshots` branch. If a local or remote `screenshots` branch exists, delete it, reupload screenshots with `upload-screenshot`, and update affected issue comments. For backend-only changes, state screenshots are not applicable.
 
 ### 4. Verify Acceptance Criteria
 

docs/PROCESS.md

@@ -164,6 +164,30 @@ Guidelines:
 - UI tests should start with Django view/template tests. Add Playwright only for critical user/operator workflows once the UI is substantial.
 - Capture screenshots only for UI issues with visible page changes. For backend-only issues, tester should explicitly state screenshots are not applicable.
 
+## Screenshot Upload Workflow
+
+Use the shared sandbox screenshot uploader for throw-away screenshot links. Do not create or update an orphan `screenshots` branch.
+
+For UI-visible issues:
+
+1. Save screenshots under `.tmp/` in this repo.
+2. Read `/home/alexey/git/sandbox-screenshots/README.md` before uploading.
+3. Install or refresh the CLI if needed:
+   ```bash
+   cd /home/alexey/git/sandbox-screenshots
+   ./install.sh
+   source ~/.bashrc
+   ```
+4. Upload each screenshot:
+   ```bash
+   upload-screenshot /home/alexey/git/datamailer/.tmp/screenshot.png
+   ```
+5. Copy the returned `url` value into the GitHub issue comment, QA report, designer audit, or PM acceptance notes.
+
+Do not paste `SCREENSHOT_UPLOAD_TOKEN` into chat, logs, commits, issue comments, or docs. Screenshot objects are temporary and expire automatically.
+
+If a local or remote `screenshots` branch exists, delete that branch, reupload the relevant screenshot files with `upload-screenshot`, and update any issue comments that pointed at the old branch URLs.
+
 ## Datamailer Engineering Rules
 
 - Do not send email from HTTP request handlers. Enqueue durable work.

docs/testing-guidelines.md

@@ -74,4 +74,13 @@ Use `Stubber` to assert:
 
 Start with Django view/template tests. Add Playwright only when the UI workflow is critical and cannot be verified well with Django tests.
 
+For UI-visible changes, save screenshots under `.tmp/` and upload them with the sandbox screenshot CLI:
+
+```bash
+cd /home/alexey/git/sandbox-screenshots
+upload-screenshot /home/alexey/git/datamailer/.tmp/screenshot.png
+```
+
+Read `/home/alexey/git/sandbox-screenshots/README.md` before uploading. Do not use an orphan `screenshots` branch. If a local or remote `screenshots` branch exists, delete it, reupload screenshots with `upload-screenshot`, and update affected issue comments.
+
 For backend-only issues, screenshots are not applicable; tester should state that explicitly.