One of my Orca eval tasks ran on a read-only workspace. Every write failed, the model's own reply said it was blocked, and orca exec still exited 0 with status success.
v0.5.16 fixes that. Headless runs get a report_blocker tool: read-only dir, missing creds, no network, and the
