Summary

Implements message:received and message:sent events for the internal hooks system, bridging from the existing plugin hooks.

Closes #8807

Changes

• Added message to InternalHookEventType
• Created typed events: MessageReceivedHookEvent, MessageSentHookEvent
• Added type guards: isMessageReceivedEvent(), isMessageSentEvent()
• Bridged plugin hooks → internal hooks in dispatch-from-config.ts and deliver.ts
• Added tests for new hooks
• Updated docs/hooks.md with new events documentation

Use Cases

• Memory/RAG integration (auto-recall before response, auto-capture after)
• Conversation logging and analytics
• Content filtering (pre/post processing)

Testing

• 115 tests passing
• No TypeScript errors
• Tested error handling (hook failures don't break message flow)

Example Hook

// ~/.openclaw/hooks/message-logger/handler.ts
const handler: HookHandler = async (event) => {
  if (event.type === 'message' && event.action === 'received') {
    console.log(`Message from ${event.context.from}: ${event.context.content}`);
  }
};
export default handler;

Greptile Overview

Greptile Summary

This PR extends the internal HOOK.md-based hook system with a new message event type, adds typed message:received / message:sent event shapes + type guards, and bridges existing plugin message hooks into internal hooks from the inbound dispatch path (src/auto-reply/reply/dispatch-from-config.ts) and outbound delivery path (src/infra/outbound/deliver.ts). Tests were added for the new type guards and handler dispatching, and docs were updated to describe the new message events.

Key integration points:

• Inbound: after extracting message metadata, it still triggers the plugin message_received hook and additionally emits an internal message:received event.
• Outbound: after delivering payloads, it triggers the plugin message_sent hook and emits an internal message:sent event.

Issues to address before merge:

• Outbound hooks currently always emit success: true and only when results.length > 0, which can misreport sends in bestEffort/partial-failure scenarios.
• Both inbound and outbound internal events can be emitted with an empty sessionKey fallback, making correlation unreliable.

Confidence Score: 3/5

• This PR is mergeable after fixing a couple of correctness issues in outbound/internal hook event emission.
• Core changes are localized and covered by unit tests, but the outbound message_sent bridge currently misreports success in partial-failure scenarios and both bridges may emit empty session keys, which can break downstream hook consumers relying on correlation.
• src/infra/outbound/deliver.ts, src/auto-reply/reply/dispatch-from-config.ts

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}