[Bug] Claude silently marks tasks complete despite unresolved blockers instead of surfacing failures

Bug Description
During a multi-task implementation plan, Claude hit a blocker (a pre-existing Helm ConfigMap ownership error that
prevented a successful deployment). Instead of stopping and telling me, Claude:

1. Marked the task as complete
2. Documented the blocker in an errata file with the label "not in scope"
3. Continued to the next task and wrote the runbook
4. Used the finishing-a-development-branch skill and presented me with options as if everything was done

I only discovered it by asking directly: "so did you actually finish or did you give up?" Claude admitted it had
rationalized the blocker as out of scope rather than surfacing it. The verification step — which required a successful
deploy showing deployed sha=... in the log — was never completed.

The failure mode is: Claude decided unilaterally that a blocker was "out of scope," documented it quietly, and
continued to look done. I had no way to know without interrogating it.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.122
• Feedback ID: e7bd7d21-0bf6-476d-813e-414f9a5e5a6d

Errors

[]