| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Successful in 6m16s
A reversal returned money on a lone grant only, and a hold taken up again after a restart began with nothing drawn, so a capture made before the restart could no longer be reversed after it. - Runtime: reverse_capture_chained returns the money to the hold on every link that carries a money ceiling, checking every link before changing any, so it is refused whole or applied whole. reverse_capture is now the one-link case of the same rule. adopt_hold takes what captures drew and reversals have not returned. - Receipts: append_reversal_chained; an open hold reports drawn_minor, the money its captures drew net of reversals. - Agreed terms: a reopened quote-bound hold carries drawn_minor, and ConditionalHolds::reverse takes a reversed part out of what counts as paid toward the payee's minimum. - SPEC 8.1: a reversal applies to a chain as to a lone grant; a hold taken up again keeps what was drawn. C32 checks the chain case. - lifecycle.json gains a delegate's hold captured, reversed through the chain and settled; verify_lifecycle.py has a fault for a reader that returns a chained reversal on the leaf only, and refuses it. Seeded faults, each caught: a chained reversal on the leaf only; a reopened hold forgetting what was drawn; a quote-bound reversal still counted as paid; a restore recounting drawn money; a chained reversal past what one link drew. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| src | ||
| Cargo.toml | ||