feat(semaino): expose canonical alerts and live intel operator state

[forkwright]

Finding

Phase 03 requires semaino to own canonical alert identity, deduplication,
severity, routing, and live akroasis intel status/alerts/baseline operator
surfaces. Current main still reports the semaino path as unimplemented, and no
live issue owns the complete alert-to-operator acceptance after tracker scope
is reconciled: #84 owns mesh topology and mesh commands, while #400 owns the
application-wide collector lifecycle.

Desired correction

Wire the production semaino alert pipeline and the intel commands through one
typed state/query boundary.

• Give each alert a stable canonical identity and apply bounded deduplication,
  severity classification, and routing exactly once in semaino.
• Make intel status, intel alerts, and intel baseline read the live
  runtime/semaino state rather than fixed zero-state or not-implemented output.
• Reuse the accepted Phase 03 collector lifecycle and signal path; do not add a
  second registry, aggregator, or raw-signal correlation path in the CLI.
• Preserve explicit empty, unavailable, stale, dropped, and backpressured
  states instead of fabricating healthy zero values.
• Protected intel reads consume accepted security(runtime): authorize direct effects through one validated caller context #409 caller/consumer context plus
  immediate Semaino capability/persona/security(signals): enforce typed sensitivity and minimized evidence at the canonical pipeline #406 disclosure checks. Invalid
  authority yields zero protected output; accepted and denied access produces a
  bounded, coalescible minimized receipt without alert content, location,
  query, topology, configuration, path, or secret.

Done when

• Deterministic fake collectors deliver source-attributed signals through the
  accepted application lifecycle into semaino, producing canonical alerts with
  fixture-verified identity, deduplication, severity, and routing.
• The three akroasis intel surfaces expose matching live status, alert, and
  baseline state, including explicit empty/unavailable behavior, without
  hardware.
• Direct caller and typed owning-workflow fixtures prove protected access
  denial/acceptance, zero output on invalid authority, and bounded/coalesced
  receipt propagation without a second interface access-log mechanism.
• Restart, duplicate input, stalled-consumer, and bounded-drop fixtures prove
  the operator view cannot diverge silently from the canonical semaino state.

Boundary

#84 retains mesh topology and mesh status/send/nodes; #400 retains the global
collector supervisor; #406 owns canonical signal disclosure behavior; #409
owns the shared caller type/resolver. This issue owns semaino alert-to-operator
integration and its domain access receipts, not those mechanisms. No hardware
use is authorized by this issue.