Date: 2026-08-08 (Day 56). Context: ran the cycle171-banked INV-1/2/3 on Origin ARM (arm-oeth) after unblocking the build. All PASS = empirically-tested WALK.
forge soldeer install was the entire cycle171 blocker. A recon-grade WALK had banked 3 invariants "scheduled, blocked on soldeer deps." One command (forge soldeer install) resolved it; forge build then exit-0. Lesson: a build "blocker" on a soldeer/foundry project is usually just an un-run dependency install - try it before deferring the whole invariant test to "next cycle."Unit_MultiAssetARM_Shared_Test (real ARM proxy + real MockAssetAdapter cross-price config + 4 base assets + LP/donation helpers). Writing INV-1/2/3 as a 90-line test that is Unit_MultiAssetARM_Shared_Test gave a FAITHFUL harness (real accounting, real adapter valuation) in minutes, and inherited their mocks/actors/config. A hand-rolled harness would risk an UNFAITHFUL setup (worse than no test - the anti-overclaim trap of a green test that doesn't model the real system). Always look for the project's Shared/Base/Setup test scaffold first.base -> adapter.requestRedeem -> pendingRedeemAssets -> claimRedeem) x privileged setCrossPrice interleaving needs a STATEFUL invariant handler (foundry invariant_ + targetContract), not a stateless fuzz. Documented as the exact residual + scheduled, per the 24-hour rule (a banked test that's run + a named residual, not "save and forget").An "empirically-tested WALK" is strictly more valuable than a "recon-grade WALK": it converts a source-read hunch into a reproducible artifact (DriftInvariants.fuzz.t.sol) that (a) defends the no-finding call under the anti-overclaim floor, (b) is a re-runnable regression check if the target ships new adapters, and (c) is Securva audit collateral. Bank the test file as a receipt, not just the verdict.