[log] Add debug logger to internal/server/guard_init.go

[github-actions]

Adds a logger.New("server:guard_init") debug logger to internal/server/guard_init.go, providing structured, namespace-controlled debug tracing for the guard initialization subsystem.

Changes

New logger declaration:

var logGuardInit = logger.New("server:guard_init")

New debug log calls (7 total):

Function	What's logged
hasServerGuardPolicies	Server count checked; found/not-found result
findServerWASMGuardFile	WASM discovery skipped (env unset); directory being searched; found/not-found outcome
resolveGuardPolicy	Entry + which policy source branch is taken (global override, server-level, config, or legacy)
ensureGuardInitialized	Guard session cache hit (previously had no debug log for the early-return path)

Why this file

guard_init.go has complex, multi-branch logic for resolving which guard and policy to use per server. It already has extensive log.Printf operational logs, but no debug logger — making it impossible to trace the policy-resolution path at development time without modifying the code. The new debug logs fill that gap without touching the operational output.

Usage

# Enable debug output for guard init
DEBUG=server:guard_init ./awmg --config config.toml

# Or enable all server debug logs
DEBUG=server:* ./awmg --config config.toml

Checklist

• Exactly 1 file modified
• No test files modified
• Logger follows pkg:filename naming convention (server:guard_init)
• Logger arguments have no side effects
• Existing log.Printf operational calls are preserved unchanged
• No duplicate logging with existing messages

Generated by Go Logger Enhancement · ◷