Revision 5 of 16
Adds a Completion step: walk every user journey in a real Chromium browser before declaring the app done.
+4 −3 lines of text vs revision 4 (this site's diff)
| Old | New | Change | Line |
|---|---|---|---|
| @@ -189,8 +189,9 @@ | |||
| 189 | 189 | ||
| 190 | 190 | 1. Run `npm run lint`, `npm run typecheck`, `npm test`, `npm run test:e2e`, and `npm run build`. | |
| 191 | 191 | 2. Start the production build and confirm the app responds. | |
| 192 | − | 3. Confirm active, anonymous, and deleted data survives restart. | |
| 193 | − | 4. Review this entire instruction and fix every missing or incorrect requirement. | |
| 194 | − | 5. Repeat affected validation. | |
| 192 | + | 3. In a real Chromium browser, complete every user journey: anonymous publication; login/logout for both users; owned-list create/edit/drag-reorder/delete/restore; non-owner denial; public links/QR/sharing; themes; and desktop/mobile layouts. | |
| 193 | + | 4. Confirm active, anonymous, and deleted data survives restart. | |
| 194 | + | 5. Review this entire instruction and fix every missing or incorrect requirement. | |
| 195 | + | 6. Repeat affected validation. | |
| 195 | 196 | ||
| 196 | 197 | Report what you built, assumptions, architecture, exact command results, and anything incomplete with its reason. Do not claim a check passed unless you ran it successfully. | |