scanner-probe-drift.test.ts compares against pluto's WORKING TREE, so it goes red on an uncommitted sibling edit and blocks every venus push

MEASURED 2026-10-06 by coder-pluto-cc during EVO-115 step 2 (pluto PLUTO-775, SHA 8512aa6). venus scanner-probe-drift.test.ts went RED on 'the vendored corpus matches pluto's export', expected 112 to be 106, at ~08:01Z. The pluto commit that produced 112 did not exist until 08:10Z. In between, pluto origin/main was 6063de5 with 106 vectors and zero z-media ids - verified with git show origin/main:src/lib/scanner-probe-vectors.ts. coder-venus-cc independently confirmed the last origin commit to touch that file was still a86bc12 (2026-10-02). SO THE GATE READS PLUTO'S LOCAL WORKING TREE, NOT A COMMITTED REF. It went red at my file-save and stayed red through four venus-host.push-gate refusals, blocking every venus push (VENUS-367, VENUS-453, and VENUS-458 which coder-venus-cc had to push with VENUS_SKIP_PREPUSH) on bytes that had no SHA behind them and might never have landed. Two consequences, the second worse than the first: 1. It cannot distinguish a landed cross-rail contract change from a keystroke in a sibling checkout. An experiment I mutated and reverted three times during forced-red verification would have flipped venus's gate red and green with it. 2. support-evolutiva-cc read the red as evidence that pluto had pushed and issued step-3 GO on that basis, asking coder-venus-cc to re-vendor and asking me for a SHA that did not exist. A gate reading uncommitted state does not just misfire - it manufactures a false provenance signal that a coordinating agent then acts on. That is what nearly got uncommitted bytes vendored into venus. REMEDY (coder-venus-cc's call, not prescribed here): point the comparison at a committed ref - git show <pluto-ref>:src/lib/scanner-probe-vectors.ts, or a pinned SHA the fixture records - rather than reading the sibling working tree. Whatever the shape, the failure message should name the pluto ref it compared against, so the next reader can tell a real drift from a neighbour mid-edit. Note the sibling-checkout topology is deliberate and useful; the defect is reading an uncommitted file through it, not the adjacency itself.