[dddd-jh]

The sequencer can drop buffered LiDAR frames at end of input even when the final IMU message already covers them. After emitting one covered frame it resumes reading the input iterator; if that iterator is exhausted, it exits before emitting the remaining ready frames.

This adds continue after a frame is emitted so the next iteration checks the buffer again before reading more input. The existing strict IMU coverage condition remains unchanged.

Per the maintainer's feedback, the PR now contains only the one-line change in the package. The regression tests used for the original validation are retained locally rather than included in this patch.

Validation: the original 11 regression cases had three failures before the fix and all passed afterward; the complete 53-case Python suite and Ruff checks passed with the added local tests. That validation used the current Python source with the published RKO-LIO 0.4.0 Windows native extension; I have not rebuilt the full C++ extension or run a ROS node locally.

[mehermvr]

Thanks for the fix. I'll just take the one line change in the package proper. no need for a test.

[dddd-jh]

Thanks! I've reduced the PR to the one-line change in the sequencer and kept the regression checks locally.

[dddd-jh]

Thanks for reviewing and merging the fix! Message ID: ***@***.***>