mvogt99

Files, sockets, subscriptions, or other finite resources are acquired without a guaranteed release path.

External input flows into sensitive operations without being checked for type, shape, range, or sanitization.

Code handles only the happy path — external calls, I/O, and parsing have no failure handling and crash on anything unexpected.

Code returned as "done" is actually a stub — a placeholder body, a TODO comment, or a function that claims completion without real logic.

Code calls functions, classes, or methods that don't exist — either on project types or on third-party library APIs.

A fix is proposed without first identifying the root cause; the symptom is masked rather than resolved.

Analysis compares options thoroughly but doesn't pick one — the decision is punted to the reader without guidance.

Analysis presents a single option without comparing alternatives or articulating the costs of the chosen approach.

Code uses a symbol that isn't imported, or imports a symbol that doesn't exist in the source module.

Reply cites file paths, directories, or module locations that do not exist in the current project.

The reply ends mid-sentence or mid-code-block because the model hit a token limit or was cut short.

Internal reasoning from <think> blocks leaks into the final user-facing reply instead of being stripped.

Shared mutable state is accessed from concurrent contexts without synchronization, producing nondeterministic behavior.

A Python function uses a mutable object (list, dict, set) as a default argument, sharing state across calls in a way that produces silent bugs.

Context window is near capacity, causing the model to drop earlier content silently and produce degraded, partial, or inconsistent output.