features/wallet/in_flight_sends_section library

Classes

InFlightSendsSection

The DURABLE in-flight two-step cue (#309): a payment whose first leg (the unshield to a wallet-controlled one-time address) is broadcast but whose send has not completed. The post-send result screen already said "don't send it again" — but that screen is dismissible, and during the forwarding window (the double-pay temptation window) the wallet screen would otherwise show only an ordinary pending tx. This cue repeats the ONE permanently-true instruction until the send completes (row deleted) or strands (the recoverable surface takes over). Aggregate + amount-only (§5.4 — no recipient/address/txid); the amount annotates the SAME pending payment the activity list shows, never additional money. Hides on empty and on the cold load. A READ FAILURE is NOT hidden (#308a, S2 §3.5d): a vanished cue is the same frame as "nothing is mid-flight", the one state that tells the user nothing about re-sending, so the failure renders an honest "could not check — retrying" line instead (the reader keeps the container retry and re-pulls on every sync/resume edge). No money depends on this line — tx0 stays visible in the activity list, and the core's fence, not this read, guards a rescan — so it carries no button.