RevowAnchor: the suite is green, and it is still not deployed
Sixteen tests pass, including three invariants checked across 128,000 calls each. The deployments table stays empty until there is an address.
The contract specified in RVW-7 is written and tested. Thirteen unit and fuzz tests cover the event, the empty root, the same day anchored twice, two publishers that never collide, the withdrawal and its timestamp, the refusal of a second withdrawal, the fact that a withdrawal only ever touches the caller, and that it is permanent a year later. Two more check that the contract refuses ether and has no fallback, so there is no hidden entry point.
Three invariants run against a handler bounded to five actors and eight claim identifiers, each checked across two hundred and fifty six campaigns of five hundred calls. No reverts, no failures. What they establish is the property that matters: a withdrawal cannot appear, move or vanish without its subject, and anchoring never writes to the withdrawal map.
None of that is a substitute for an independent read of fifty lines of Solidity, and it is not presented as one. A test suite written by the same person who wrote the contract tests the same assumptions twice.
It is not deployed. The source and the ABI are published, the deployments table in RVW-7 is empty, and it stays empty until there is an address to put in it.