v13.106.0

v13.106.0 - 2026-10-07

• 🎉 CoreEvents & CoreDevices now carry multiple external IDs keyed by system (ie: { "active911": "1234", "caltopo": "B42325" }) in a new core_entity_external table, returned as external_ids
• 🚀 POST & PATCH /api/core/event & /api/core/device take a single external_id: { system, value } which is merged into the record's external IDs - an empty value removes the system - a bare string is still accepted as the default system and echoed on the deprecated external_id response field
• 🚀 The CoreEvent & CoreDevice Layer Mappings map the External ID as a system & value pair - the value defaults to the Feature ID and the system to default, which is where existing external IDs are migrated to - Mappings saved with the bare string form are migrated & still accepted
• 🚀 Layer submissions UPSERT on the external ID within the Connection, kind & system, serialised by an advisory lock
• ✅ Add API & Mapping tests for multi-system external IDs

�