fix(mount): reduce websocket polling overhead

[khaliqgant]

Summary

• wire the fsnotify file watcher into the relayfile mount CLI path so local writes sync on change instead of requiring the two-second scan loop
• skip no-op polling cycles while websocket mode is active, leaving periodic reconciliation every 10 intervals
• apply the same quiet-cycle behavior to the standalone relayfile-mount poll mode

Tests

• go test ./...

---

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bc28b73eeb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep polling when websocket transport is disconnected

When --websocket is enabled, this branch skips nine out of ten timer ticks entirely, so no sync runs on those ticks. That regresses fallback behavior: if websocket setup fails or later disconnects, SyncOnce is no longer called each interval to poll (sync only polls when wsConn == nil), so local uploads and remote pulls can be delayed by up to websocketReconcileEvery*interval instead of the configured interval. This same pattern is also present in cmd/relayfile-mount/main.go, so both entrypoints throttle polling even when websocket is unavailable.

Useful? React with 👍 / 👎.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.