feat(coredeno): Tier 2 bidirectional bridge — Go↔Deno module lifecycle
Wire the CoreDeno sidecar into a fully bidirectional bridge:
- Deno→Go (gRPC): Deno connects as CoreService client via polyfilled
@grpc/grpc-js over Unix socket. Polyfill patches Deno 2.x http2 gaps
(getDefaultSettings, pre-connected socket handling, remoteSettings).
- Go→Deno (JSON-RPC): Go connects to Deno's newline-delimited JSON-RPC
server for module lifecycle (LoadModule, UnloadModule, ModuleStatus).
gRPC server direction avoided due to Deno http2.createServer limitations.
- ProcessStart/ProcessStop: gRPC handlers delegate to process.Service
with manifest permission gating (run permissions).
- Deno runtime: main.ts boots DenoService server, connects CoreService
client with retry + health-check round-trip, handles SIGTERM shutdown.
40 unit tests + 2 integration tests (Tier 1 boot + Tier 2 bidirectional).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
af98accc03