[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.

Some sites are separate systems on OpenMHz, each with its own key, which is common when each was a Trunk Recorder system. When an older setup is upgraded, those sites become one system that keeps the first site's OpenMHz settings. Without this change, every site's calls would then upload to the first site's OpenMHz system.

What changes

• New setting: each system's settings have an optional Sites of their own list: the site's name, its OpenMHz API key, and its name on OpenMHz. The name defaults to the site's name, which after the upgrade is the old system's short name, usually its OpenMHz name too.
• Routing: a call kept from a listed site goes there; other sites' calls go to the system's.
• Validation: a listed site must have a name and a key, otherwise the plugin won't start and says which site.
• Docs: the README explains sites, the upgrade, and 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 the default name, an explicit name, fallback to the system's settings, and a site missing its key. All 14 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