A Sandbox Sensor measures the kinds you tick #115

Parent

#27 (M6 General sensors)

Spec: docs/specs/general-sensors.md (added by PR #111; read it there until it merges). Parent: #27.

What to build

The Sandbox's Node list reports, per Sensor, the kinds it declares, and overall the kinds the current Event offers (flood kinds, its tracks, and camera). Adding or editing a Sensor through the Sandbox API takes an optional kinds list; a kind not on offer is refused with a readable sentence. A new Sensor declares everything on offer except camera; the first Sensor also declares camera. A Sensor's declared kinds are asked for at each share. The Sandbox Panel shows tick boxes per Sensor row (phone-width usable, per design-rules). A Sensor remembers what was unticked; an Event switch applies the new offer, a Region switch starts new Sensors with nothing unticked. Spec decision 3.

Acceptance criteria

• The Sandbox Panel lists each Sensor's kinds; unticking one stops that kind in the next reading and /api/state stops listing it.
• A kind not on offer is refused by the API with a readable sentence.
• A new Sensor declares everything on offer except camera; the first Sensor also declares camera.
• After a Region or Event switch every Sensor's kinds are within the new offer.
• Only kinds the playing Event supplies are on offer (plus camera).
• scripts/check.sh passes.

Blockers are native links.