MVC v0.1.9

Improved waypoint-count validation for linked checkpoint bug cases.

This release removes the old blanket +1 waypoint-count allowance and replaces it with a proper structural check against the map itself. The checker now scans waypoint data and only accepts a waypoint-count shortfall when the map contains an invalid linked checkpoint group (LinkedCheckpoint with order -1 / 4294967295).

What changed:

• Exact waypoint-count matches still validate normally
• One missing waypoint per lap is only tolerated when the broken linked checkpoint bug is actually present on the map
• Added invalidLinkedCheckpointOrders to --data-dump output for easier debugging
• Updated README documentation to match the new logic

This makes validation stricter for unrelated mismatches while still correctly handling maps affected by the broken linked checkpoint bug.