atrium 0.37.1

A patch release: the bus reaches the people it should, and the CLI explains itself.

A bus event wakes the panes it addresses and the topic's subscribers. The bus was pull only: a finished worker's bus pub work status=done sat unseen until the lead happened to run bus feed, and a worker's --to lead was dropped silently by the subtree rule. Seen in a live fleet, where the builder came up, read the feed once, found nothing addressed to it and went idle for good. An event is now typed into every pane subscribed to its topic and every pane it names with --to (a comma list is fine), once each is idle, as one framed line: [atrium bus #68 fyi from teammate "builder" on "work" — not operator input] item=F20 status=done. Who may wake whom: the publisher's own subtree, the panes above it, and any pane that subscribed — never an unrelated pane by name. Wakes are sanitized (no control, bidi or zero-width characters; a body cannot open a second frame), capped apart from ctl send, and coalesced per pane. Roles are unique while a pane lives.

Agents learn it from the CLI. The directive every claude pane receives says to run bus topics, subscribe to what its role must react to, and aim a hand-off with --to. atrium --help, ctl, fleet, config, recover and reap all answer --help/-h from anywhere, in one shape.

The atrium skills (marketplace plugin 0.2.8) subscribe first, address hand-offs with --to, start rosters from atrium fleet init, and describe config.json.

Full details in the CHANGELOG.