fix: avoid top-level await in bun-runner so hooks load on Node < 14.8

[Kurama2d]

Problem

plugin/scripts/bun-runner.js is an ES module that uses a top-level await:

const stdinData = await collectStdin();

Top-level await is unsupported by the ESM loader of Node < 14.8. On hosts where Claude Code invokes hooks with an older Node — e.g. the Node 12 that ships with Ubuntu 22.04 and many WSL setups — the module fails to load before running anything:

file:///.../claude-mem/.../scripts/bun-runner.js:128
const stdinData = await collectStdin();
                  ^^^^^
SyntaxError: Unexpected reserved word
    at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)

This breaks every claude-mem hook (e.g. the Stop hook surfaces it as a hook error) for those users.

Fix

Wrap the body after collectStdin() in an async IIFE so await is no longer at module scope. No behavior change on modern Node.

This is the same oldest-Node compatibility concern the file already handles deliberately for optional chaining — see the ?. note above isPluginDisabledInClaudeSettings().

Repro / verification

# Under Node 12:
node --check plugin/scripts/bun-runner.js

• Before: SyntaxError: Unexpected reserved word
• After: parses OK (verified on v12.22.9)

[greptile-apps]

Greptile Summary

This PR removes top-level await from the Bun hook runner. The main changes are:

• Wraps stdin collection and child process startup in an async IIFE.
• Keeps existing argument handling, stdin forwarding, diagnostics, and exit behavior unchanged.
• Preserves compatibility with older Node ESM loaders that cannot parse top-level await.

Confidence Score: 5/5

Safe to merge; the change is narrowly scoped to moving existing asynchronous startup logic out of module scope.

The modified file preserves the existing control flow and behavior while improving compatibility with older Node ESM loaders.

T-Rex Logs

What T-Rex did

• T-Rex ran the code on Node 12 at the base revision and observed an exit code of 1 with a SyntaxError: Unexpected reserved word at const stdinData = await collectStdin().
• T-Rex re-ran the code on Node 12 at head and observed an exit code of 0 with no parse errors.
• T-Rex also checked Node v20.9.0 at head and observed an exit code of 0 with no parse errors.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "fix: avoid top-level await in bun-runner..." | Re-trigger Greptile}