Lezama context/token telemetry -> venus canonical store

Elazar 2026-08-16. monitor-context.sqlite on venus holds 31 agents, ALL venus - zero lezama and zero whey rows. So monitor-context-cc cannot analyse lezama token/context efficiency at all; any such report today would be invented. Lezama runs its own, deliberately different (more abrupt) ss//compact protocol, with several agents at a 450k pre-auto-compact cap for less-interrupted client work - Elazar wants that variant measured and compared against the venus actuator. Needs: a write path for lezama context samples + actuator events into the canonical telemetry store (this project's Postgres 'telemetry', NOT a second sqlite). Respect Term 1 - no cross-host reads; lezama pushes, venus does not pull. Interim: lezama sends a one-off report by DM (requested 2026-08-16). Owners: one-db PM bin-whey-cc for the store/schema; bin-lezama-cc + nw-lezama-cc for the lezama side; monitor-context-cc consumes. mem:project_monitor_context_venus_actuator