fix: route LEPUS global events to GlobalEventEmitter

[KealanAU]

Summary

globalEventFromLepus lifecycle events (e.g. keyboardstatuschanged) never reached the background thread. This routes them into GlobalEventEmitter.

• Wraps tt.OnLifecycleEvent to forward LEPUS lifecycle events to GlobalEventEmitter, preserving any existing handler.
• Adds useGlobalEvent() composable with automatic scope cleanup (onScopeDispose).
• Exports useGlobalEvent from the runtime entry; adds a regression test + patch changeset.

Verification

• pnpm test; biome clean on touched files.
• Confirmed native keyboardstatuschanged reaches useGlobalEvent('keyboardstatuschanged', ...).

Note: pnpm --filter vue-lynx run build stops at the pre-existing types package error (elements/index.ts can't resolve vue) — unrelated to this change.

[vercel]

@KealanAU is attempting to deploy a commit to the huxpro's projects Team on Vercel.

A member of the Team first needs to authorize it.

[KealanAU]

CleanShot.2026-06-17.at.21.29.21.mp4

[Huxpro]

Looks good to me.

One follow-up I'd still like to see is a regression test that explicitly proves the previous tt.OnLifecycleEvent handler is preserved when vue-lynx installs its wrapper, since keeping that compatibility path intact is part of the behavior change here.

[KealanAU]

Added a regression test: it installs the wrapper over an existing tt.OnLifecycleEvent and asserts both our routing fires and the prior handler is still invoked. (4468f0a)