PiClaw v2.6.10 — Broadcast News

PiClaw v2.6.10 — "Broadcast News"

Re-release notice: v2.6.10 has been retagged to 4facdeba3ad79f446441d27027cf6ab2eef5d35b, adding the Earendil 0.79.7 dependency bump on top of the Broadcast News release.

A tools patch about cross-session messaging and control: the chat relay stays awake by default, sessions can be steered from elsewhere, and identity resolution stops acting like a gossip columnist with a regex.

Features

• The chat relay is now active by default, so cross-session messages do not require every operator to remember which invisible switch was responsible for letting one branch talk to another.
• Cross-session session control is now available through tools, giving operators a proper way to inspect and steer sessions across branches instead of relying on ritual, luck, and remembering which tab was shouting.
• Session-control, status, activation, capability, and chat-tool runtime coverage were expanded around the new tool paths, because distributed agent control without tests is just improv theatre with permissions.

Fixes

• Chat relay identity resolution is hardened so target sessions and agent names resolve more predictably, with fewer opportunities for the wrong branch to receive a surprise memo.
• Peer-message rendering was tightened around cross-session relay behaviour, because once messages can cross rooms, the UI should not look like it discovered that fact from a rumour.

Under the hood

• Earendil packages were bumped to 0.79.7, keeping the shared runtime stack current and ensuring the plumbing gets its own tiny paperwork parade.
• A dedicated chat-tool runtime layer was added to keep relay behaviour deterministic and easier to test.
• Session-control tooling now plugs into startup and extension registration alongside session-status, tool-activation, and capability surfaces.
• Hook determinism and feature-regression coverage were updated so the built-in tool catalogue remains boring in the best possible sense.
• Classic web bundles were rebuilt for the relay/session-control changes.

Known issues

• Cross-session control is still power tooling; it can reduce tab-hopping, but it cannot make distributed work emotionally tidy.
• Naming sessions clearly remains advisable, because no amount of relay hardening can redeem a fleet of tabs all called “default”.

Upgrade

• Upgrade normally; no migration step is required.
• If cross-session messaging feels less like passing notes through a ventilation duct, that is intentional.