dingtalk-event

Run `dws event +listen-im --kind at-me` to subscribe to messages that @mention the current OAuth user. Wait for the `[event] ready` marker on stderr before reading NDJSON events from stdout.

Use `dws event consume` with one or more of the seven OA EventKeys such as `user_oa_approval_task_created` or `user_oa_approval_instance_finished`. These subscriptions use `ruleType=all` and accept no user, group, or filter parameters.

Yes, `+listen-im --kind sender` accepts `--user`, `--open-dingtalk-id`, or `--user-query`, and `--kind group` accepts `--chat-id` or `--chat-query`. Names are resolved uniquely inside the CLI and fail before creating any subscription on zero or multiple matches.

First confirm the correct `[event] ready` marker appeared on stderr, then check `dws event status` for the subscribe_id and received/dropped counters. Messages sent by the current user are filtered by self-loop protection, so test with another user or bot.

Subscriptions follow a 0/2/1 retry budget based on the retryable flag and honor `retry_after_seconds`, `in_flight`, `cooldown`, and `terminal_hold` states. Local protection records reset after 24 hours without failures, and `terminal_hold` lasts one hour.

Run `dws event stop <subscribe_id> --dry-run` first to preview the impact, then confirm with `--yes`. Never use `kill -9` on the consumer process because it skips automatic unsubscription cleanup.