feat: live camera/video feed observations for common-operating-picture workflows

[mikemcdougall]

Problem Summary

Extracted from the demo-capability program epic (#2310, transferred to honua-demo) so the server-side item is not lost. The SensorThings observation model and protocol surface now exist on trunk (Honua.Protocols.SensorThings, IObservationStore, Postgres store), but there is no way to register and serve live camera/video feeds as first-class observed streams alongside sensor observations — the remaining gap in the "real-time sensors + camera feeds" capability track. This is a differentiator for gov common-operating-picture (COP) / 911 scenarios.

Why This Matters Now

The honua-io/honua-demo#17 demo program identified this as "the real gap" in the sensor-handling track; the sensor half has since shipped, leaving camera feeds as the only unhomed server work item. Parking it as a scoped roadmap issue keeps the backlog honest after the epic's transfer to the demo repo.

Acceptance Criteria

• A camera/video feed can be registered as an observed datastream (metadata: location, orientation/FOV where known, stream URL/protocol) via the shared metadata/control-plane pipeline.
• Feed metadata is discoverable through the SensorThings surface (and/or STAC where imagery-adjacent) without inventing a protocol-local catalog.
• Feed liveness/staleness is observable (health status surfaced like other realtime feeds).
• Integration tests cover registration, discovery, and status per ADR-0011.

Capability Key(s)

cap/streaming

Affected Repo(s)

honua-server (honua-console for COP display; honua-sdk-js consumption — follow-on)

Gate Tier Impact

None initially — new feature area, tests join the standard tiers when implemented.

Release/Deploy Impact

None until implemented; no migration or config change in this issue.

Non-Goals

• Video transcoding, recording, storage, or analytics (serve/reference streams, don't process them).
• Reimplementing the SensorThings observation model (exists) or moving-object track fusion (Real-time moving-object track fusion (ADS-B / AIS / GPS) #2440).
• Any demo.honua.io enablement (owned by honua-demo).

Follow-on Split Guidance

Split console COP display and SDK consumption into honua-console / honua-sdk-js issues once the server contract exists.

Priority

P3

Additional Context

Related: #2434 (promote SensorThings to GA), #2440 (moving-object track fusion). Origin: capability track in the demo program epic honua-io/honua-demo#17.

[github-actions]

Capability key(s) not recognized

These capability key(s) don't match a known cap/<category> prefix: cap/streaming.

If the key is just more granular than our category list knows about, that's fine — this is a heads-up, not a blocker. Known categories: ai, alerts, analytics, caching, channels, collaboration, control-plane, demo, disaster-recovery, discovery, editing, enrichment, extensibility, field-ops, geocoding, identity, import, ops, printing, process, raster, routing, scene, serve, static-map, streaming, styling, temporal
(see docs/gis/data/capability-categories.seed.json). Feel free to correct the field or ignore this if the key is intentional.