[Feature]: no event for workboard card status changes - hook bus has no workboard events, notification kinds limited to completed|failed|stale

Version

OpenClaw 2026.6.11

Summary

There is no way to react to a workboard card changing status. The internal hook bus has no workboard events at all, and the workboard notification channel only emits three terminal kinds. Anything that needs to act on an arbitrary transition (for example ready -> running, or a card entering blocked) has to poll.

What exists today

The hook event table in docs/automation/hooks.md lists command:*, session:compact:*, session:patch, agent:bootstrap, gateway:startup|shutdown|pre-restart, and message:*. No workboard or card events. Confirmed by search across the docs and by the workboard plugin manifest, which declares only a tools contract and commandAliases, with no hooks contribution.

The workboard's own notification subscriptions (workboard_notify_subscribe and friends) are the closest mechanism, but the accepted kinds are limited to:

completed, failed, stale

So terminal outcomes and staleness are covered; ordinary transitions are not. The plugin does compute a transition kind internally (archived, unarchived, diagnostic, and so on) when diffing a card, so the information exists at the point of change - it just is not exposed on either bus.

Request

Either of:

• add a card lifecycle hook event (e.g. workboard:card:status) carrying card id, board id, previous status, and new status, or
• widen the accepted notification kinds beyond completed|failed|stale to cover status transitions, including blocked and archived.

Why

Without it, the only way to observe the board is to poll workboard_list on a timer. In our setup that produced several scheduled jobs whose entire purpose was to notice a transition that the plugin already detects internally. A push signal on either bus would remove that class of job outright.