[robotastic]

Trunk Recorder Pro now has systems with sites (TrunkRecorder/trunk-recorder-pro#51; SDK trunk-recorder-plugin 0.4.0). A call heard on several sites is saved once, and its JSON says which site it was kept from (site). Settings, including this plugin's, now belong to the system.

Broadcastify Calls often has a system per site, which is how Trunk Recorder sets it up: a system per site, each with its own broadcastifySystemId. When an older setup is upgraded, those sites become one system that keeps the first site's Broadcastify settings. Without this change, every site's calls would then upload under the first site's system ID.

What changes

• New setting: each system's settings have an optional Sites of their own list: the site's name, its Broadcastify system ID, and its API key if it isn't the system's. A call kept from a listed site goes to that site's system; other sites' calls go to the system's.
• Validation: a listed site must have a name and a system ID, otherwise the plugin won't start and says which site is missing what.
• Messages: refusal messages and the startup log name the site.
• Docs: the README explains sites, and how to set them up after the upgrade or when coming from Trunk Recorder's multiSite.
• Versions: built with trunk-recorder-plugin 0.4.0; version 0.1.5.

Tests: new test a_site_of_its_own covers routing by site, falling back to the system's key, and a site missing its system ID. All 15 tests pass, and clippy and cargo fmt --check are clean.

Release after merge: tag v0.1.5, then a registry PR.

🤖 Generated with Claude Code