mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Maurice
9ce8b7ea9e
Cases appended to four existing suites for the lines this branch left unrun: the fold state and the map places it hides, the owner-based via anchor, the day seam and the proportional geometry slicing, and the live roadtripVia:changed events. With the four new suites in the commits before this one, coverage of the lines this branch adds goes from 69 % to 96 %, measured the way the gate measures it — the routed lines against the diff, not a file average. Every added case was mutation-checked: the rule it claims to pin was broken in the source and the case had to fail. Two of them found real defects rather than missing coverage, and both are fixed here. A via dropped on the incoming night drive went to the wrong leg. The guard for it asked the insert index whether the point lay before the card's first stop, and that index cannot answer: insertIndexForAlong clamps to at least 1 for any card with two stops or more, and the rail publishes no other kind. So the branch read correctly and never ran, and a via on the night stretch was filed after the first drawn stop — the route ran forward, doubled back to the point and carried on, which is exactly what the comment above it said must not happen. Asked of the distance instead. The two one-field writes the rail offers, the stop kind and the fill level, went straight to the API while their neighbour checked place_edit first. The server refused them, so nothing was ever saved, but a reader got an error toast for touching a control that should not have acted.