fix: isolate intent classifier from gateway

[giscebot]

Summary

• run enqueue-time intent classification with openclaw agent --local
• support the current OpenClaw JSON shape with top-level payloads
• keep timeout errors concise and avoid persisting the complete prompt
• clarify which operations still need gateway concurrency headroom

Root cause

Job 6433 ran while the OpenClaw gateway was reporting codex app-server startup timed out, database is locked, and event-loop stalls around 60 seconds. Increasing gateway concurrency does not protect classifier calls from those gateway-wide failures.

The current OpenClaw CLI also returns successful local responses as top-level payloads; the bridge only recognized result.payloads, causing valid responses to normalize to confidence zero.

Validation

• 73 focused tests passed
• real local classifier call with openai/gpt-5.6-luna returned an applied classification at 0.99 confidence
• git diff --check