Summary

• Moves unmentioned group/channel room-event classification into core under src/channels/inbound-event/*, with shared classification, context, event-kind, and media helpers.
• Migrates Telegram, Slack, Discord, Synology, gateway/tooling, prompt context, and MCP metadata from inbound-turn naming to InboundEventKind / inbound-event terminology.
• Adds canonical config messages.groupChat.unmentionedInbound: "room_event" and deliberately removes the pre-ship ambientTurns spelling with no runtime alias or migration.
• Bumps the gateway protocol to v5 for inboundEventKind, including MCP header/env rename to x-openclaw-inbound-event-kind / OPENCLAW_MCP_INBOUND_EVENT_KIND, plus Android/Swift generated model updates.
• Keeps only public plugin SDK compatibility aliases in openclaw/plugin-sdk/channel-inbound; all bundled plugins are migrated to the modern API.

Fixes #81317.

Behavior addressed

Core, plugin-agnostic inbound room-event classification for unmentioned always-on group/channel chatter. Mentions, DMs, commands, abort requests, and native commands remain user_request; configured unmentioned group/channel chatter can become room_event, run as quiet context, avoid normal visible source replies, avoid Discord status/ack reactions, and speak visibly only through the message tool.

Implementation notes

• src/channels/inbound-event/classification.ts owns classifyChannelInboundEvent and resolveUnmentionedGroupInboundPolicy.
• src/channels/inbound-event/context.ts builds inbound event prompt context and emits InboundEventKind.
• Discord, Slack, and Telegram now consume the same core classifier instead of duplicating plugin-local policy.
• Room events set prompt metadata such as inbound_event_kind: room_event and visible_reply_contract: message_tool_only, suppress transcript-only assistant persistence, and force source reply delivery to message_tool_only.
• Public SDK legacy helpers still map inboundTurnKind and return InboundTurnKind; this is the explicit public-plugin-API compat exception, not an internal compat layer.

Codex review

• Ran /Users/steipete/Projects/agent-scripts/skills/codex-review/scripts/codex-review against the branch diff before the final fixup.
• Accepted and fixed prior review findings: legacy public buildChannelTurnContext now returns InboundTurnKind, Slack/Discord room events stay message_tool_only, Slack/Discord abort phrases stay user_request, and Discord room events do not emit ack/status reactions.
• Final rerun: /Users/steipete/Projects/agent-scripts/skills/codex-review/scripts/codex-review on the local fix diff returned codex-review clean: no accepted/actionable findings reported.
• Rejected runtime config aliasing for ambientTurns: this branch has not shipped, repo policy keeps runtime config canonical, and legacy repair belongs in doctor/migration paths only.

Verification

• git diff --check
• pnpm docs:list
• pnpm config:docs:check
• pnpm plugin-sdk:api:check
• pnpm protocol:check
• pnpm check:test-types
• pnpm build
• pnpm test src/plugin-sdk/channel-inbound.test.ts extensions/discord/src/monitor/message-handler.process.test.ts
• Focused full surface test command: pnpm test src/plugin-sdk/channel-inbound.test.ts src/channels/inbound-event/classification.test.ts src/channels/inbound-event/context.test.ts src/channels/inbound-event/media.test.ts src/config/zod-schema.visible-replies.test.ts src/auto-reply/reply/prompt-prelude.test.ts src/auto-reply/reply/get-reply-run.media-only.test.ts src/auto-reply/reply/dispatch-from-config.test.ts src/gateway/mcp-http.test.ts src/gateway/tool-resolution.test.ts src/gateway/server-methods/send.test.ts extensions/telegram/src/bot-message-context.require-mention.test.ts extensions/telegram/src/bot-message-context.reactions.test.ts extensions/telegram/src/inbound-event-delivery.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/action-runtime.test.ts extensions/discord/src/monitor/message-handler.preflight.test.ts extensions/discord/src/monitor/message-handler.process.test.ts extensions/slack/src/monitor/message-handler/prepare.test.ts src/auto-reply/reply/source-reply-delivery-mode.test.ts
• Blacksmith Testbox via Crabbox: tbx_01krrehj2sys4bmh2qxwh01z78, Actions run https://github.com/openclaw/openclaw/actions/runs/25962778077. pnpm check:changed passed through conflict-marker, changelog attribution, wildcard reexport, duplicate coverage, dependency/patch guard, typecheck core/core tests/extensions/extension tests, lint core/extensions/scripts. Testbox app lint stopped only because the image lacked swiftlint.
• pnpm lint:swift locally passed. Existing non-fatal macOS type body length warnings remain; iOS lint was clean.

Real behavior proof

Behavior addressed: Unmentioned always-on group/channel chatter is classified in core as a quiet room_event, while explicit requests keep user_request behavior.

Real environment tested: Local macOS checkout plus Blacksmith Testbox through Crabbox (tbx_01krrehj2sys4bmh2qxwh01z78).

Exact steps or command run after this patch: Ran the local docs/config/protocol/SDK/type/build checks, focused Vitest coverage across core/Telegram/Slack/Discord/gateway reply behavior, final codex-review, and Testbox pnpm check:changed via node scripts/crabbox-wrapper.mjs.

Evidence after fix: Focused Vitest passed 603 tests before final review fixup; post-fix targeted pnpm test src/plugin-sdk/channel-inbound.test.ts extensions/discord/src/monitor/message-handler.process.test.ts passed 61 tests; Testbox check lanes were green until the missing swiftlint binary; local pnpm lint:swift passed.

Observed result after fix: Core emits InboundEventKind, bundled plugins use the core classifier, Discord no longer leaks visible reactions for room events even with explicit status reactions, and public legacy SDK callers still see InboundTurnKind.

What was not tested: Live Telegram, Slack, or Discord provider E2E. Testbox app lint could not complete because swiftlint is missing from that image; the same Swift lint lane was covered locally.