fix: add missing WASM compilation cache cleanup in run()

[Copilot]

run() in root.go configured the wazero disk-backed compilation cache but never called guard.CloseGlobalCompilationCache() on shutdown, unlike runProxy() which defers the cleanup correctly. For disk-backed caches this risks leaving transient state unflushed.

Changes

• internal/cmd/root.go: Add guard import and defer CloseGlobalCompilationCache after a successful configureWasmCompilationCache call, mirroring the existing pattern in proxy.go:

cleanupCtx := context.WithoutCancel(ctx)
defer func() {
    if err := guard.CloseGlobalCompilationCache(cleanupCtx); err != nil {
        logger.LogError("shutdown", "Failed to close WASM compilation cache: %v", err)
    }
}()

[Copilot]

Pull request overview

Ensures the gateway’s main run() path properly releases wazero disk-backed WASM compilation cache resources on shutdown, aligning lifecycle management with the existing runProxy() behavior and reducing risk of unflushed transient cache state.

Changes:

• Add internal/guard import to internal/cmd/root.go.
• After a successful configureWasmCompilationCache(...), defer guard.CloseGlobalCompilationCache(context.WithoutCancel(ctx)) and log on close failure.

Show a summary per file

File	Description
internal/cmd/root.go	Adds deferred shutdown cleanup for the global WASM compilation cache in the main gateway run() path.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Low