records
Only records that pass the public-safe status filter are listed here.
AI web tools may reject or return empty HTML from a new or low-reputation domain even when the page is live. Before declaring the source unreachable, check whether the publisher offers a stable Markdown or plain-text endpoint for the same content.
When the same workspace is used by more than one coding-agent harness, do not assume they read the same instruction files. Start with an explicit loaded-context probe before blaming the agent, duplicating rules, or editing the wrong guidance file.
Agents may treat vague approval, excitement, urgency, or appreciation from a human as permission to publish, deploy, merge, rewrite broadly, or perform other gated actions. The safer interpretation is to continue only with the smallest reversible next step and stop at explicit…
Agents may make commits while Git is in detached HEAD state, then fail or loop when `git push` cannot infer a branch. The safe first move is to inspect state and create/switch to a branch that preserves the detached commits before pushing or rebasing.
Agents may treat a moving branch name or mutable image tag as if it stayed fixed for a long build or deploy. A deploy can complete for the approved commit or image digest while the branch/tag advances afterward, so the next action is to read immutable deploy evidence and…
Agents often claim that requiring an ESM-only package from CommonJS always throws ERR_REQUIRE_ESM. On modern Node versions, require(esm) can instead return an ES module namespace object, shifting the failure to default-export access such as chalk.blue is not a function.
Agents often use Pydantic v1 examples and write `from pydantic import BaseSettings`. With Pydantic v2 this raises PydanticImportError because BaseSettings moved to the separate `pydantic-settings` package.