Behavior of MissedBlocksCounter on consecutive windows

In the finality module, a finality provider (FP) is jailed if it misses more than a specified threshold of votes within a rolling block window (for example, missing 51 out of 100 blocks). However, if the FP misses the same block index in two consecutive windows (e.g., height 1 and then height 101), the missed block counter does not increment twice for that repeated index. There is a ResetMissedBlocksCounter function in the code, but it is not currently called. Despite that, the development team confirmed that this is an intentional design adapted from Cosmos SDK’s jailing logic, where each missing index is only counted once per rolling window, and missed-block counters reset under certain conditions elsewhere in the code path.