fix(organizer): avoid blocking FUSE I/O during symlink reconciliation

[samtruman]

Summary

The filename-mode reconciliation introduced in #133 calls realpath() while comparing provider-backed sources. On FUSE/debrid mounts, that filesystem I/O can block when the remote is slow or unavailable, delaying or freezing organizer startup and scans.

This follow-up keeps source-alias reconciliation for ordinary filesystem paths, but avoids realpath() for paths under the configured provider mount. Those paths are compared lexically within the shared mount namespace, so reconciliation remains non-blocking.

Scope

• generic organizer behavior;
• no provider-specific paths or deployment configuration;
• no changes to media selection or naming policy;
• preserves existing reconciliation behavior for local filesystem paths.

Validation

• organizer filename tests: 6 passed;
• unit suite: passed;
• typecheck: passed;
• git diff --check: passed.

This supersedes the unsafe filesystem-I/O behavior in closed PR #133.

[moderniselife]

Hi @samtruman — #131, #132, and #136 are all merged into develop. Thanks again! 🎉

Notes from the merge:

• fix(organizer): avoid blocking FUSE I/O during symlink reconciliation #136 targeted main, so I retargeted it to develop to match the repo flow (it's a follow-up to fix(organizer): reconcile filename mode symlinks #133, which only lives in develop) — it'll ride the next release. It came back CONFLICTING after the retarget, so I resolved the two hunks in organizer.ts keeping both your FUSE non-blocking early-outs and the existing realpath fallback/versioning, verified with typecheck + organizer tests before merging.
• fix(providers): keep configured backup providers inactive #131 touches registry.ts, so I re-ran the SSRF regression suite after merging — all green.
• One still-open heads-up: the mount-readiness macOS-local failure noted on feat: reconcile newly added provider media into Arr libraries #114 is unchanged (Linux CI green).