docs: add message dispatch config keys to config-reference

[chaodu-agent]

Summary

Add message_processing_mode, max_buffered_messages, and max_batch_tokens to the [discord], [slack], and [gateway] sections in config-reference.md.

Also add corresponding Helm value mappings (messageProcessingMode, maxBufferedMessages, maxBatchTokens).

Why

These keys are documented in message-dispatch-modes.md but were missing from the config reference, making it hard for users to discover them.

Changes

• docs/config-reference.md: Added 3 rows to each adapter table + 3 Helm mapping entries

[github-actions]

⚠️ This PR is missing a Discord Discussion URL in the body.

All PRs must reference a prior Discord discussion to ensure community alignment before implementation.

Please edit the PR description to include a link like:

Discord Discussion URL: https://discord.com/channels/...

This PR will be automatically closed in 3 days if the link is not added.

[shaun-agent]

OpenAB PR Screening

This is auto-generated by the OpenAB project-screening flow for context collection and reviewer handoff.
Click 👍 if you find this useful. Human review will be done within 24 hours. We appreciate your support and contribution 🙏

• Title: docs: add message dispatch config keys to config-reference
• Source: docs: add message dispatch config keys to config-reference #834
• Status: moved to PR-Screening
• Generated at: 2026-05-17T12:44:45.216Z
• Discord thread: not available

Screening report

screened PR #834 and moved the project item from `Incoming` to `PR-Screening`.

GitHub comment: #834 (comment)
Project action: openabdev/1 item PVTI_lADOEFbZWM4BUUALzgs9z1E now has Status PR-Screening.

Intent

Document message dispatch config keys missing from docs/config-reference.md.

Feat

Docs work: adds message_processing_mode, max_buffered_messages, max_batch_tokens, and Helm mappings.

Who It Serves

Deployers and agent runtime operators.

Rewritten Prompt

Update docs/config-reference.md with the dispatch config keys for Discord, Slack, Gateway, and Helm. Verify names/defaults against dispatch docs, config structs, and Helm templates.

Merge Pitch

Low-risk docs consistency fix. Main concern is accuracy of defaults and Helm paths.

Best-Practice Comparison

OpenClaw/Hermes do not materially apply; this is config documentation, not scheduling/runtime architecture.

Implementation Options

Conservative docs-only verification, balanced docs plus cross-links, or ambitious generated/checked config reference.

Comparison Table

Included in the posted comment.

Recommendation

Balanced path: verify values, keep the rows, and add a cross-link to message-dispatch-modes.md if easy.