Add webhook HTTP server for message queueing

[jlia0]

Summary

This PR adds a webhook HTTP server to the queue processor, enabling external systems to submit messages via HTTP requests instead of only through file-based queue operations.

Key Changes

• New HTTP Server: Implemented a webhook server listening on a configurable port (default 3077) using Node's built-in http module
• Webhook Endpoints:
  • POST /webhook/message — Accept JSON payloads to queue new messages with validation
  • GET /webhook/health — Health check endpoint returning queue statistics and uptime
  • GET /webhook/status/:messageId — Query the status of a queued message (queued, processing, completed, or not found)
• Message Handling: Webhook messages are validated, assigned unique message IDs, and written to the incoming queue directory for processing
• Configuration: Webhook port is configurable via .tinyclaw/settings.json with a sensible default
• Security & Robustness:
  • Request body size limit (1MB) to prevent abuse
  • CORS headers for broad compatibility
  • Proper error handling and logging
  • Input validation for required fields (channel, sender, message)
• Dependencies: Added http and crypto imports for server implementation and message ID generation

Implementation Details

• Message IDs are generated using a combination of channel, timestamp, and random hex bytes for uniqueness
• The server gracefully handles port conflicts and logs appropriate warnings
• Queue status checks scan all three queue directories (incoming, processing, outgoing) to provide accurate message state
• All webhook operations are logged for debugging and monitoring purposes

https://claude.ai/code/session_01Dcg3mDHsjpH6vzsqce15GU