The order note in suggestNumber is the kind of detail that saves a support ticket: stripping US thousands separators before treating a lone comma as a decimal. One case we would add to the tests is a value like "1.234,56", where the period is the thousands separator and the comma is the decimal. Neither branch catches it as written, so it falls through as not a number, which is safe, but the suggestion step could offer "1234.56" when the delimiter detection already points to a semicolon file. Flagging ambiguous dates instead of guessing is a rule we wish more importers followed.