Fix: claim the credited swap-to-WIRE payout instead of waiting on a balance

[heifner]

Companion to Wire-Network/wire-sysio#558 (SEC-150). The swap-to-WIRE flow fails against that branch until this lands.

sysio.reserv::paywire now credits a claimable balance rather than pushing sysio.token::transfer. It settles inside the never-throw consensus dispatch chain, where a pushed transfer let the recipient's on_notify handler abort the delivery — the chain runs notified receivers with no exception isolation.

flow-swap-to-wire polled the recipient's WIRE balance until a deadline, which can no longer become true: the payout sits in sysio.reserv custody until pulled. It now waits on the claimable balance and calls claimwire, so bridging into WIRE is settle-then-claim.

WireClient gains claimWire / claimPay and their claimable-balance readers. Those read the tables raw rather than through the typed contract-table accessor, because the new tables do not reach the typed surface until @wireio/sdk-core publishes the regenerated SysioContractTypes (Wire-Network/wire-libraries-ts#66). The doc comment names the exact call to switch to once that version is released.

Flows deliberately unchanged, having been checked:

• flow-swap-from-wire never exercises a revert, so refundwire is not on its path — only the escrow leg, which still pushes from the user.
• flow-reserve-lifecycle's WIRE assertions cover the matchreserve escrow, also still a user push.
• flow-emissions-soak covers sysio.dclaim staker claims, which were already pull-based.

The custody assertion in the swap-to-WIRE flow still holds because the claim happens in the preceding step; that dependency is now stated in a comment rather than left implicit.

[jglanz]

nit: inline lambda await should use a factory pattern

[heifner]

Nit addressed in 5742a26: the claimable poll is now a named claimableReached(ctx, account, target) beside underwritersActive, with the call site passing () => claimableReached(...) — matching the shape the other read-backed polls in this scenario already use. No behaviour change; prettier-clean and no new type errors.

Flagging for a re-approval since require_last_push_approval is on and the branch was CLEAN before this push.

[jglanz]

You shouldn't have try to fix my nit picking lol

function claimableReachedPredicate(
  ctx: SwapScenarioContext,
  account: string,
  target: bigint
): AsyncFunction<boolean> {
  return () => ctx.wire.getWireClaimable(account).then(amount => amount >= target)
}

[heifner]

lol, ok

[heifner]

Done in 2ca9733 — claimableReachedPredicate(ctx, account, target) returns the bound predicate and pollUntil takes it directly, no inline lambda.

One substitution: AsyncFunction isn't exported anywhere in the tree (not @wireio/shared, not @wireio/cluster-tool, not the deps), so the return type is spelled () => Promise<boolean> — pollUntil's own predicate parameter type. getWireClaimable returns Promise<bigint> and target is a bigint, so the .then narrows as expected.

underwritersActive is left as-is: it predates this PR on master, so converting it would widen the diff past the review.