build(omo-senpi): regenerate the committed extension bundles

The bundle freshness gate rebuilds from source and compares, so a source change that does not
ship its regenerated bundle fails `senpi-compatibility (ubuntu-latest)` - the only leg that
runs the check.

Rebuilt on linux/amd64 with the node runner the gate itself uses. The bundler takes its externals
from the running runtime's builtinModules and its output is host-shaped besides, so a bun build,
or a node build on another platform, produces bytes the gate rejects. `build-extension.mjs --check`
and `build-install.mjs --check` both pass there.