## What?
Handles previously ignored daemon startup errors in `daemon/daemon.go`:
- checks `os.Remove` when cleaning up a stale daemon socket, while
ignoring `os.IsNotExist`
- checks `os.Chmod` when setting daemon socket permissions
- wraps both failures with contextual error messages
## Why?
Closes #714
Closes #719
Ignoring these errors could either hide stale socket cleanup failures,
leading to confusing daemon startup errors, or leave the daemon socket
with unintended permissions if `chmod` failed. Returning explicit errors
makes startup failures clearer and keeps socket permissions handling
safer.
---------
Co-authored-by: FromSi <fromsi665@gmail.com>