VENUS-422 wiring: call context-persist-sensor.sh from the venus statusline + install context-persist-hook.sh

VENUS-422 shipped the scripts (sh.git a9ccbff: context-persist-sensor.sh, context-persist-hook.sh, context-persist.test.sh, 16 controls green) and was closed, but NOTHING IS WIRED - the scripts are inert until the statusline calls the sensor. Closing 422 left no row tracking that, which is how this work silently does not land for the third time. TWO EDITS, both on venus, both runtime-lane: 1. ~/.claude/statusline-elazar.sh - add one line where the payload is still in $INPUT: printf '%s' "$INPUT" | context-persist-sensor.sh >/dev/null 2>&1 || true The sensor is byte-silent and always exits 0 (controls [5] and [6] assert exactly that), so it cannot corrupt or break the bar. The file is untracked, host-local and Elazar's, which is why bin lane did not edit it. 2. ~/.claude/settings.json - add context-persist-hook.sh as a second UserPromptSubmit hook, alongside the existing llmmsg-bootstrap-session.sh. THEN SETTLE THE ONE UNVERIFIED FIELD. .session_id is measured present in the STATUSLINE payload but was never measured in a UserPromptSubmit payload - no prompt could be induced during the build. Without it the hook no-ops rather than guessing which session's marker to fire. After wiring, submit any prompt and check: ls ~/.local/state/context-persist/no-session-key Absent = the field is carried and the actuator is live. Present = the field is missing on that surface and the hook needs a different session key; tell bin-venus-cc and it is a code change, not a wiring one. Defaults: fires at 78% of CLAUDE_CODE_AUTO_COMPACT_WINDOW (250000 on venus), re-fires after another 20000 tokens, state in ~/.local/state/context-persist/. Knobs all carry the CCM_ prefix per failure #12. Verify live with: tail the marker file while a session climbs.