pr-testlisted

# Manual E2E Test Test a PR/branch end-to-end by building the full platform, interacting via browser and API, capturing screenshots, and reporting results. ## Critical Requirements These are NON-NEGOTIABLE. Every test run MUST satisfy ALL the following: ### 1. Screenshots at Every Step - Take a screenshot at EVERY significant test step — not just at the end - Every test scenario MUST have at least one BEFORE and one AFTER screenshot - Name screenshots sequentially: `{NN}-{action}-{state}.png` (e.g., `01-credits-before.png`, `02-credits-after.png`) - If a screenshot is missing for a scenario, the test is INCOMPLETE — go back and take it ### 2. Screenshots MUST Be Posted to PR - Push ALL screenshots to a temp branch `test-screenshots/pr-{N}` - Post a PR comment with ALL screenshots embedded inline using GitHub raw URLs - This is NOT optional — every test run MUST end with a PR comment containing screenshots - If screenshot upload fails, retry. If it still fails, list failed files and require manual drag-and-drop/paste attachment in the PR comment ### 3. State Verification with Before/After Evidence - For EVERY state-changing operation (API call, user action), capture the state BEFORE and AFTER - Log the actual API response values (e.g., `credits_before=100, credits_after=95`) - Screenshot MUST show the relevant UI state change - Compare expected vs actual values explicitly — do not just eyeball it ### 4. Negative Test Cases Are Mandatory - Test at least ONE negative case