fix(daemon): log host disk-full side-effect failures at warn level

[posthog]

Problem

• A full disk on a user's machine becomes an Autter error-tracking issue. The team must triage it, but no Autter code failed.
• ingest_trace_payload_fast and the command side-effect path log every side-effect failure with tracing::error!. SentryLayer turns each ERROR event into an AutterError exception.
• The only skip, is_missing_working_dir_error, matches vanished temp repos. It does not match std::io::ErrorKind::StorageFull (ENOSPC on Unix, ERROR_DISK_FULL on Windows).

Changes

• A new is_storage_full_error classifier selects host disk-full errors. At the two side-effect failure sites, these errors now log at warn level, and SentryLayer does not capture warn-level events.
• The daemon still calls record_side_effect_error, so family state still shows the failure. Only the log level changes.
• The warn messages have a separate name (...: host disk is full), so the logs show this environment cause clearly.

Site	Before	After (disk full)
async side-effect error	ERROR → exception	WARN, not reported
command side effect failed	ERROR → exception	WARN, not reported
Other errors at both sites	ERROR → exception	No change

Note

Out of scope: the async completion log write failed sites can also fail on a full disk, but this change does not touch them. Also, this change does not overlap #64, which widens is_missing_working_dir_error for missing git objects. The two changes edit different functions and can merge in any order.

Testing

• cargo test --locked --lib -- storage_full_error missing_working_dir_error: 5 passed. This includes the new storage_full_error_detects_disk_full_io_errors test, which uses raw os error 28 on Unix.
• cargo fmt --check: clean. cargo clippy --locked --lib: no new warnings. The existing warnings are on lines that this change does not touch.
• Skipped: the full task test daemon-mode suite. CI runs it.

Agent context

• The report names autter-monorepo, but the daemon code is in this repo.
• Rejected option: skip disk-full failures in maybe_apply_side_effects_for_applied_command, as the code does for vanished directories. That would return Ok and hide a real side-effect failure from family state. A lower log level keeps the record and removes only the noise.

---

Created with PostHog Desktop from this inbox report.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}