Monitor a hull

Watches one hull and emits vessel_risk.changed when its sanctions status, ownership opacity, or vetting grade moves. Re-screened every 24 hours — the cadence matches how often the underlying lists actually publish, so a shorter interval would spend quota re-reading the same file. The first run establishes a baseline and emits vessel_monitor.ready, never a change event. Each run consumes one screening unit.

With a TEST key the monitor is created but never scheduled and never metered: next_run_at comes back null and no screening runs. Drive it with POST /api/v1/vessel-monitors/{id}/simulate to fire a real vessel_risk.changed event at your endpoint on demand, which is how you prove a handler works before going live.

Required scope: vessel:monitor.