also, it references `SGXClient#register_handler_before`, which was
removed in a previous commit, so this code would throw if it ever ran

slightly nicer dev experience, although beware that Solargraph might
break on ruby 3.4

* 'print-as-we-go' of https://git.secluded.site/sgx-bwmsgsv2:
  Print --recent events as we seek

don't worry, i checked and this property test doesnt add appreciable
time

--recent seeks from newest events to oldest, so printing as we seek instead of
batching and printing in reverse changes this flag's message ordering to mirror
seek ordering: newest to oldest.

basically, add FakeFs and set MMS_{PATH, URL}, then fix things that
those two broke

as such, resulting nil/"" + fix tests:
- guard s.body with .to_s in to_catapult_possible_oob
- accept OOB-only stanzas in message handler guard
- fix tests that don't handle nil/empty message_body
- fix the main handler's guard to accept stanzas with a body OR media
- test_invisible_separator fixed, needed to bypass changes to the body
  from XML roundtrip
- discovered unholy geometries in webmock's JSON parsing

i suspect, but have no evidence, that this is motivated by
EM::HttpClient

The following changes since commit 111ceaa651dea6a6c82555e8e7f0fcfb2b18fbfb:

  backport: handle non-exceptions in `panic` (2026-03-26 11:42:34 -0400)

are available in the Git repository at:

  https://gitlab.com/phdavis1027/sgx-bwmsgsv2.git 7658ce847544ccb59c6ccd4ce9f9717d5582a75e

for you to fetch changes up to 7658ce847544ccb59c6ccd4ce9f9717d5582a75e:

  URI.parse all the things (2026-03-28 11:43:25 -0400)

----------------------------------------------------------------
Phillip Davis (2):
      explicitly verify_peer in `call_catapult`
      URI.parse all the things

 sgx-bwmsgsv2.rb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

* 'resend-all-and-multiple' of https://git.secluded.site/sgx-bwmsgsv2:
  Add multiple numbers, file input, --all to resend-inbounds

Accept repeatable --number flags and --file for bulk number lists. Add
--all to resend to every customer, gated behind interactive confirmation
(type y/yes) or --force. Abort in non-TTY without --force.

Widen the event filter to match both 'in' and 'thru' messages, since
both are inbound from the customer's perspective.

Validate that --all is mutually exclusive with --number/--file, and that
at least one targeting option is always provided.

- previous code used `.then` on a non-promise, which doesn't work on
  ruby 2.7
- also, early-return case failed to consider resend events, fixed that