Post-closure force-capture exposureCards & Interchange

Task prompt

hey, can you dig into something for me when you get a sec? ops was venting in #banking that we keep seeing force-captured card charges hit accounts after customers have already closed them, and it's quietly bleeding us. finance wants a real number for the risk review. across every closed account, can you figure out how much these post-closure force captures have actually cost us, i mean the charges that genuinely settled. heads up that "force capture" is just how ops talks about it — don't go looking for a card-event label spelled that way, because the ones that hurt us are the charges that actually completed and pulled money, whatever the event is labelled as. and please pull the numbers from the card-network event stream (card_events), not from the posted transaction ledger (trans) — the ledger mixes holds and releases and will undercount. once you've identified the settlement/clearing status, don't further subset by message_type — finance wants every settled event after closure, not just the ones labelled auth-capture. a few more ground rules so finance and i don't end up arguing about whose number is right: go off when the charge landed on our own ledger rather than the network's timestamp, treat post-closure as after the closure was finalized and not from when the customer first asked to close, and on the event count include the settled ones that came through at zero dollars — ops cares how often this happens, and those obviously don't move the dollar total. while you're in there, how many separate closed accounts got hit? also let me know who the processor on the hook for clearing these is, and whether there's anything we can do on our end to stop them — answer that one as just true or false. drop it back to me as one JSON object with these keys: card_processor, post_closure_capture_usd, post_closure_capture_count, accounts_affected, can_prevent. thanks!