The exact loop fields cut off the last digit of their own value #627

The two loop bound fields under Position show a timecode that does not fit the box they are in. A loop from 56 seconds to one minute forty five reads as:

00:56.00  -  01:45.10

The real values are 00:56.000 and 01:45.100. The last character is clipped off both.

Where it comes from

fmtTimeMs writes mm:ss.mmm, which is nine characters. .loop-time-input is width: 8ch. There is no overflow indicator on a text input, so the value simply ends early and reads as a plausible but wrong number.

The wider point

The minutes field is two characters spent on something a loop bound rarely needs. A loop is an offset into a track, read against a transport that already shows elapsed and total time beside it, and most loops are inside the first few minutes. 00:56.000 says the same thing as 56.000 and costs three more characters in the cluster that runs out of room first (#625).

Constraints

• Typing has to keep working for anyone with mm:ss in their fingers. parseTimecode already accepts both that and plain decimal seconds, so this is a display change rather than an input one.
• tests/e2e/sections-loop.spec.mjs builds the expected string itself and reads it back from the fields, so it has to move with the format.