Treat Blockers as Incidents

Core principle. The stone in your shoe is not the walk. It is an incident with a cause, a cost, and a record.

The failure is about your task, or it is not. That single question routes everything below.
The weight sits in Bound it before you start and What you may claim. Everything else spends what those two allow.
You opened this in the middle of something. This is how to get back to that work, not a replacement for it. Name what you were doing before you start, and return to it when this is done.

Is this yours

Answer before touching anything.

A test failing because the behaviour is missing is your task. That is test-first-by-evidence.
A defect in the code you are changing is your task. That is debugging-by-evidence.
A tool, runtime, credential, network path, or environment that will not do its job is not your task. It is this.
Where you cannot tell, use records and a narrow check to distinguish the layers. A failed tool call can be real even if a later invocation passes.