Fix macOS File Provider mount EDEADLK

[aseembits93]

Summary

• tolerate macOS File Provider EDEADLK only for a not-yet-materialized direct child of the already-inspected trusted provider root
• preserve fail-closed behavior for existing files, symlinks, non-provider projections, deeper paths, and all other errors
• document the compatibility rule and add regression coverage for the accepted and rejected cases

Verification

• cargo fmt --all -- --check
• cargo test -p locality-store
• cargo test -p loc-cli --test mount
• cargo clippy -p locality-store --all-targets (passes with existing repository warnings)
• git diff --check

Closes #217

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
locality	Ready	Preview	Aug 19, 2026 10:51pm

[aseembits93]

@codex review

[github-actions]

Codex review

No high-confidence issues found.

[aseembits93]

Signed macOS verification reached and passed the issue-specific boundary: mount registration no longer returns EDEADLK, the binding persists, and packaged localityd starts and watches the new mount.

Evidence: https://github.com/codeflash-ai/locality/actions/runs/32305613555

The next failure is downstream visible-folder materialization, not alias inspection. A separate long-state-path harness gap discovered during verification is tracked in #220. Automated review reports no high-confidence issues, and all completed PR checks are green.