fix(mcp): drop unreachable throw in setTimeout-wrapped initial sync

[mvanhorn]

Summary

Drops a throw error inside the initial-sync setTimeout callback in packages/mcp/src/sync.ts. The callback runs with no caller, so the throw has nowhere to propagate. The preceding console.error(...) is the terminal signal for unexpected failures.

Why this matters

Reporter in #256 called out the bug with an exact file:line pointer. Unexpected errors during the 5s-deferred initial sync are silently lost today, not surfaced. This is a pure log-and-continue fix.

Changes

                 } else {
                     console.error('[SYNC-DEBUG] Initial sync failed with unexpected error:', error);
-                    throw error;
+                    // Do not re-throw here: this callback runs via setTimeout with no caller to propagate to.
                 }

No other changes. No behavior regression: the throw was already unreachable.

Testing

pnpm install --frozen-lockfile && pnpm build passes locally on Node 22.

Related sync.ts PRs

Aware of #314, #274, #268, #234 also touching packages/mcp/src/sync.ts. None of them address the setTimeout throw (#314 preserves it at the relocated line). Whichever lands first, the other rebases cleanly.

Fixes #256

[mvanhorn]

Appreciate getting the dead-code path out of the initial sync.