User will have tokens stuck closing a leverage position due to an unconsidered case

Vault inflation attack in `AutoCompoundingPodLp` is possible due to incorrectly minting dead shares

Handling tokens in the contract upon adding liquidity results in breaking the optimal one-sided supply amounts

`PodUnwrapLocker` can be drained due to an arbitrary input

Users can prevent reward accrual in order to capture rewards distributed before they have joined

`_calculateBasePerPTkn` includes debond fee twice, lowering the price too much

Removing leverage will often revert due to calling an incorrect function

Adding leverage using a podded token will lead to a revert

Leverage position can be impossible to close due to a non-initialized struct field

`_tokenToPodLp` will lower the yield of `AutoCompoundingPodLp` during volatile markets

Bad data would DOS the whole `AutoCompoundingPodLp`

`addInterest` will not update the interest acurately which would enable users to claim rewards for time that they weren't staked inside `LendingAssetVault`

Incomplete logic will allow malicious users to perpetually override the amount to swap to the minimum

`LendingAssetVault::_updateAssetMetadataFromVault()` results in incorrect calculations

Protocol assumes the same deployment on all chains on multiple occasions

MEV bots will steal from users due to an incorrectly manipulated value

Incorrect `min/maxPrice` checks

Incorrect total assets available calculation leads to incorrect utilisation

Removing leverage will often fail when the received pair LP token is insufficient

Pausing rewards will lead to tokens being bricked and users not being able to claim them

A vault can be considered not over-utilized when it is and vice versa upon depositing

Liquidations will revert incorrectly due to an out-of-sync leftover collateral value

Tokens will be stuck in `AutoCompoundingPodLp` if the intermediary swap token is not a reward token