Run a wind-down in the harness on a throwaway vault #300

Priority

Medium

User story / Problem statement

The contract interfaces are only checked by Rust tests against native code, and the harness never runs a wind-down, so the bindings generated from the deployed Wasm never meet that path. The harness should also run a wind-down on a throwaway vault. With the seven-day minimum delay, no real network can activate one at once, so the local run uses a build that drops the minimum, and the testnet run is spread over seven days (Tranche 2 release).

Expected outcome

A harness test deploys a throwaway vault set on the local network, takes it through a wind-down, and simulates every vault entrypoint through the generated client at least once.

Acceptance criteria

• Refuses to run on any network but local
• Deposit, claim, redeem request, wind-down proposal and activation, a round and a claim all succeed
• Every function in the vault's spec is called at least once

Alternatives considered

Trusting the Rust unit tests alone, since they already cover the wind-down logic. They call the contract natively and never go through the generated TypeScript client, so they cannot catch a mismatch between the deployed Wasm's real spec and the bindings the CLI generates from it.

Technical notes

Running this suite in CI comes with the CI change for the Wasm tests, in a separate change.