Set Speaker Cameras

Replace the speaker's camera mappings with this exact set.

Replace-set, not per-pair add/remove: the picker submits a set, and rewriting the whole set in one transaction makes priority reordering atomic. An empty list unmaps the speaker entirely — which immediately returns every affected camera to fail-closed behavior.

ARMING IS RE-DECIDED ON EVERY SUBMISSION. Each mapping's agent_trigger_enabled is written from THIS request, so a mapping sent without the field lands disarmed (human-triggered only) regardless of what the row it replaces said — it is never inherited. A picker that round-trips mappings must send the flag back or it will disarm the agent on every camera it re-submits, which is the safe direction and the reason this is stated here rather than left to be discovered.

This speaker's camera mappings, as they stand after the request.

ARMING IS RE-DECIDED ON EVERY REPLACE-SET PUT AND IS NEVER INHERITED. The PUT rewrites the whole set, so each agent_trigger_enabled here is what THAT request asked for: a mapping submitted without the field comes back false (human-triggered only) regardless of what the row it replaced said. Read this payload as the authoritative new state — do not assume an omitted field left the previous value alone, because it did not.