The matrix driver gains two probes over each baseline's REAL
SessionProjectionRegistry: hostile gateway usage must keep the served view
schema-valid on every later delivery (billed from the sanitized buckets),
and a poisoned upstream wire unit must reproduce the dsh containment gap -
the schema violation escapes the drive loop per event, every unit
registered after it starves, and snapshot() (every reconnect baseline)
throws wholesale. That seam is the registry's to fix; the probe names it
per generation.
Bowen Liang
4580692389