One catch per distinct rule. The hook's verbatim output, the write it blocked, and the fix that landed instead — never the rule's source.
A `return ... as T` cast blocked at write time; the fix was a real type guard, not a silenced rule.
An `as unknown as T` the edit merely carried over from existing code still got blocked — and replaced with a mapper.
A `tab.children!` blocked at write time; optional chaining went in instead.
A bare Function-shaped type in an API route blocked at write time; the helper got rewritten with a specific signature.
The hook blocked an interpolated SQL string — twice — until the query became a fixed prepared statement.
Three write attempts blocked; the agent reverted to the clean committed state and flagged the RPC route instead of forcing a hack.
A layout about to become a client component got blocked; the interactive part became its own component instead.
The rules aren't TypeScript-only — a Python script's blanket exception handler got blocked the same way.
I tried to patch something fast and wrong. The system refused the write and told me the proper move — so the shortcut never shipped.