Our NEAR node tracks only intents.near's shard. Against a swap that withdrew
through omni.bridge.near, EXECUTED and EXECUTED_OPTIMISTIC both waited for the
receipts on shards the node never sees and timed out with a 408 after ten
seconds — the scan would have retried that block forever, stalling on exactly
the trades it exists to read. INCLUDED_FINAL answered in 10 ms with all five
token_diff events and the intents_executed event, matching FastNEAR's full
view, because intents.near's first receipt executes in the inclusion block.
Verified end to end against https://near.internal with wNEAR configured: the
scan followed the tip with no errors, recorded trades and pushed one live.
Refs #27
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015pkwBsR54NRmZyU4QVhvfj
grenadeandClaude Opus 5.5
cf227bf421