Record the redemption queue on testnet #368

Priority

High — required for Tranche 2

User story / Problem statement

The Tranche 2 "Notice-period redemption queue" measure asks for testnet transactions that show the queue working: request, cancel, price, claim and a reserve-short queue. The README's "Testnet flow verification" table lists four investor flows (deposit, claim shares, redeem request, claim cash) and none of the rest. There is no transaction for a cancelled request, for pricing, or for a redemption the vault's cash does not yet cover.

Expected outcome

The README lists one testnet transaction per queue step, linked to an explorer, executed against the contract IDs in "Demo deployment".

Acceptance criteria

• A transaction for each of: request_redeem, cancel_redeem, pricing (the seal and the attestation that price the epoch), claim_redeem, and a redemption left uncovered by a short reserve
• For the reserve-short step, the transactions that show uncovered() above zero and the fund and claim that clear it
• Every transaction ran against the contract IDs currently listed in the README
• The scenario is repeatable from the harness, and the README names the command

Technical notes

• A claim refused with ClaimNotCovered fails at simulation and leaves no transaction. Decide which transaction counts as evidence of the short reserve; the priced epoch and the fund that follows are the candidates.
• The harness already seeds testnet; check whether happy-path.test.ts covers cancel and the short reserve before adding scenarios.