Greptile Summary

This PR fixes a silent hook-firing regression introduced by bundle splitting: because the bundler could emit internal-hooks into multiple chunks, registerInternalHook and triggerInternalHook were each operating on their own private Map instance, so registered handlers were never found at trigger time. The fix is to store the handler registry on globalThis.__openclaw_internal_hook_handlers__ and lazily initialise it only when the property is absent, so every chunk that imports this module shares the same Map.

Key observations:

• The approach (globalThis singleton with a namespaced key) is the standard, widely-used solution for exactly this class of bundler-deduplication problem.
• Existing helpers — clearInternalHooks, unregisterInternalHook, getRegisteredEventKeys — all operate on the shared Map reference and continue to work correctly.
• The handlers local variable is assigned without a non-null assertion (!) after the initialisation guard. TypeScript does not narrow mutable object properties through control-flow in the same way it narrows locals, so under strictNullChecks this may yield a Map | undefined type and downstream type errors. Adding ! or using ??= would make the intent unambiguous (see inline comment).
• Because globalThis persists for the process lifetime, handlers registered during module evaluation survive HMR reloads in development. This means handlers registered by a stale module version may still fire after a hot reload — a minor development-only concern that is an acceptable trade-off for the production correctness fix.

Confidence Score: 4/5

• This PR is safe to merge; it correctly fixes a real production regression with a well-established pattern and no logic changes to the hook dispatch code.
• The fix is minimal and targeted, and the globalThis singleton pattern is the correct solution for cross-chunk module deduplication. The only open concern is a missing non-null assertion that could surface as a TypeScript type error if null-check strictness is increased, but it does not affect runtime behaviour and pnpm check is currently clean.
• No files require special attention beyond the minor type-safety note on src/hooks/internal-hooks.ts line 219.

_{Last reviewed commit: 3e8bd73}

Landed via temp rebase onto main.

• Gate: pnpm test -- src/hooks/internal-hooks.test.ts src/hooks/message-hooks.test.ts
• Note: full pnpm check is currently red on unrelated main-branch failures in extensions/tlon and src/discord, src/media-understanding, src/security type checks.
• Land commit: 8fee445
• Merge commit: 68e982e

Thanks @Drickon!