bug: a released on-chain allowance payment keeps holding allowance capacity #1585

Refs:

• feat: add allowances for automatic paykit payments #1340
• feat: add allowances for automatic paykit payments #1340 (comment)

What happened?

When an automatic on-chain allowance payment's broadcast is refused or its result is unknown, the attempt is recorded as unknown in the allowance ledger. Recovery now settles it only on positive evidence from the wallet (the send attempt accepted or observed, or a verified payment proof). If the wallet later releases that send (its request ended and the coins are spent back to the wallet), the release deletes the send-attempt record and the request's proof, so recovery finds nothing to read. The attempt then stays unknown for good and keeps holding allowance capacity.

Expected behavior

A released on-chain send records the allowance attempt as failed, so its capacity returns to the allowance.

Steps to Reproduce

1. Let an allowance pay a request on-chain while the broadcast is refused.
2. After the request ends, release the unresolved send.
3. Restart the app: the allowance still counts the payment against its limit.

Bitkit Version

Unreleased: allowances branch of #1340.

Reproducibility

From the code path; not yet run on a device.