fix: add withTimeout protection to auto-recall in openclaw-plugin

[Jah-yee]

Summary

PR #688 fixed the auto-recall timeout issue in examples/openclaw-memory-plugin/index.ts by wrapping the recall logic with withTimeout(). However, the plugin code was later refactored to examples/openclaw-plugin/index.ts, and the fix was not synchronized to the new location.

Changes

1. Import withTimeout from process-manager.ts
2. Define autoRecallTimeoutMs constant (5000ms)
3. Wrap entire auto-recall logic in withTimeout to prevent indefinite blocking during transient connection issues

Impact

• Critical: Any transient connection issue causes complete, permanent agent silence without this fix
• With timeout protection, the hook will timeout gracefully after 5 seconds and allow the agent to start without memory context

Testing

• Build: npm run build in examples/openclaw-plugin/
• Manual test: Configure with autoRecall: true, have OpenViking server in transient state, send message to agent

Fixes: #748

[qin-ctx]

cc @Mijamind719

[qin-ptr]

This is a high-quality bugfix that addresses a critical regression issue.

Summary

PR #688 previously added timeout protection to auto-recall in openclaw-memory-plugin, but the fix was not synchronized when the plugin was refactored to openclaw-plugin. This PR applies the same timeout protection using the validated withTimeout() pattern.

Analysis

Design Validation:

• ✅ Problem is real: withTimeout imported but not used in auto-recall path
• ✅ Root cause correctly identified: missing timeout wrapper causes indefinite blocking
• ✅ Solution at correct layer: timeout protection in hook allows graceful degradation
• ✅ Reuses existing mechanism: withTimeout from process-manager.ts (verified in PR #688)
• ✅ Complete lifecycle: timeout throws error → caught → logged → agent continues

Code Correctness:

• ✅ IIFE properly wraps entire auto-recall logic
• ✅ 5-second timeout value validated in PR #688
• ✅ Error message updated to mention "timed out"
• ✅ No breaking changes, fully backward compatible

Testing:

• Manual test plan provided in PR description
• Same fix pattern used successfully in openclaw-memory-plugin

No issues found. Excellent work maintaining consistency with the previous fix!

🤖 I am a bot owned by @qin-ctx.