fix(server): standalone CLI builds again with Cursor usage (#71)

Upstream's Cursor usage reader (pingdotgg#10409) loads @napi-rs/keyring with a
dynamic import(). A Node single executable can only import built-ins, so
the release's build-exe check rejects the bundle. Load it through
createRequire like node-pty and fff-node.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: kalvenschraut

apps/server/src/provider/cursorCredentialStore.ts

@@ -1,3 +1,5 @@
+import * as NodeModule from "node:module";
+
 const CACHE_MS = 5 * 60_000;
 
 /** Share one Keychain request across usage history and limits in this server process. */
@@ -22,8 +24,12 @@ export function makeCachedCursorAccessTokenReader(
   };
 }
 
+// `import()` cannot load file-backed packages inside the single-executable CLI;
+// `require` reads the real filesystem.
+const requireForKeyring = NodeModule.createRequire(import.meta.url);
+
 /** Read the Cursor CLI's default macOS credential without invoking the shared security binary. */
 export const readMacCursorAccessToken = makeCachedCursorAccessTokenReader(async () => {
-  const { AsyncEntry } = await import("@napi-rs/keyring");
+  const { AsyncEntry } = requireForKeyring("@napi-rs/keyring") as typeof import("@napi-rs/keyring");
   return (await new AsyncEntry("cursor-access-token", "cursor-user").getPassword()) ?? null;
 });