Duration, Velocity, TimeSignature, Interval, Note and Tempo accept whitespace and '+' that ToString never prints: Duration.Parse(" 1 / 4 "), Note.Parse("C4: 1/4 :v 64 ") #471

What's wrong

#307 changed Pitch.TryParse to parse the octave with NumberStyles.AllowLeadingSign only. The comment at Pitch.cs:~89-93 explains why: whitespace or '+' "would parse to a pitch that prints back differently".

The sibling Music value types still use NumberStyles.Integer, which allows leading and trailing whitespace and a leading sign:

Note, Rest, ChordEvent and Progression cells inherit the same leniency.

Reproduction (all return true)

Pitch.TryParse("C 4") and Pitch.TryParse("C+4") return false, so the Music types disagree about whether to accept a non-canonical spelling.

Suggested fix / acceptance criteria

• Parse integer fields with NumberStyles.None.
• Where a sign is meaningful (Interval semitones, and a negative Duration numerator if that is kept), allow a leading - and reject a leading +. Reuse the same helper as Pitch.
• In Tempo, reject whitespace before or after the BPM.
• Tests: every input above returns false, and X.Parse(x.ToString()) == x still holds.

Related but distinct: #434 (the Duration.TryParse overflow on "-2147483648/-1").