ClawSweeper status: review started.

I am starting a fresh review of this pull request: fix: gate discord realtime voice by wake name This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

Verification before merge:

Behavior addressed: Discord OpenAI agent-proxy realtime voice can require a wake name before responding, defaulting to the routed agent display/identity name when wakeNames is unset.
Real environment tested: local OpenClaw checkout, active local gateway config with channels.discord.voice.realtime.requireWakeName=true, and GitHub CI for head SHA 205cda7.
Exact steps or command run after this patch: node scripts/run-vitest.mjs src/agents/realtime-bootstrap-context.test.ts extensions/discord/src/config-schema.test.ts extensions/discord/src/voice/manager.e2e.test.ts -t "resolveRealtimeBootstrapContextInstructions|Discord realtime voice modes|requires the agent wake name|uses configured wake names|starts Discord realtime voice in bidi mode|leaves non-OpenAI"
Evidence after fix: focused Vitest passed 3 files / 10 tests; git diff --check passed; pnpm config:channels:check passed; autoreview passed with no accepted/actionable findings; Testbox check:changed passed as tbx_01ksc12aca7bdy2d15ky9a1m85; GitHub CI run 26350984966 passed; CodeQL run 26350984980 passed; CodeQL Critical Quality run 26350984979 passed; Workflow Sanity run 26350984977 passed; OpenGrep PR Diff run 26350984975 passed.
Observed result after fix: restarted gateway logged Discord realtime bridge with requireWakeName=true, wakeNames=molty, autoRespond=false, interruptResponse=false, bargeIn=false.
What was not tested: live spoken Discord roundtrip with actual audio wake-name phrasing.