[bug] ROS1 BAG import fails with message type hash mismatch in rosbags 0.11.8

Description

After upgrading rosbags from 0.11.5 to 0.11.8, importing a ROS1 BAG fails with a message type hash mismatch. This appears related to work item #139 (closed), which fixed parsing ROS1 message fields whose names end in an underscore.

Environment

OS: Windows rosbags: 0.11.8 Python: 3.10.11

Installation: project environment managed with uv

Import fails with:

Error: Message type 'vehicle_msgs/msg/VehicleDataInput' hash mismatch aecba1cf75c676aac584c278d85f7d53 != fc9b4841fba559950483ae943aca4b38

The BAG contains VehicleDataInput fields with trailing underscores, such as vehicle_speed_.

Expected result

The reader should open the BAG and complete the header export, as it does with rosbags 0.11.5.

Could you clarify whether this hash mismatch is expected after the parser change in #139 (closed), or whether it indicates a regression in ROS1 BAG message-definition handling?