fix: repair embedded quotes before digit-prefixed tokens (e.g. "985/211")

[HANYIIK]

Problem

When a JSON string value contains an embedded unescaped double-quote immediately followed by a digit, jsonrepair incorrectly treats that quote as the end of the string. This happens because the heuristic at the end-quote detection site uses a bare isDigit(text[i]) check: if the character after a potential closing quote is a digit, the quote is assumed to be genuine.

This causes inputs like the following to throw Colon expected at position N instead of being repaired:

{"usage": "includes \"985/211\" items"}
{"label": "requires \"2fa\" enabled"}
{"version": "version \"3.0.1\" released"}

In each case the digit-prefixed token (985, 2, 3) is a fragment of a longer value, not a standalone JSON number.

Root cause

parseString (regular/jsonrepair.ts:518, streaming/core.ts:709):

// before
isDigit(text[i])

A " followed by 9 in "985/211" satisfies isDigit, so the string is cut short at that quote. The remainder (985/211"…) is then parsed at object level, 985 becomes an unquoted key, and / is found where : is expected.

Fix

Replace the bare isDigit check with isFollowedByNumber, which scans past the full number token (integer part, optional decimal, optional exponent) and only accepts the quote as a real end-of-string when the number is immediately followed by a structural JSON character (,, }, ]), whitespace, or EOF.

"985/211"  →  digit scan: 985 → next char: /  →  not structural → embedded quote → escape ✓
["a" 42]   →  digit scan: 42  → next char: ]  →  structural      → real end quote → split ✓
["a" 2.5]  →  digit scan: 2.5 → next char: ]  →  structural      → real end quote → split ✓

isFollowedByNumber is exported from stringUtils.ts for the regular parser. The streaming parser uses an equivalent inline closure (isInputFollowedByNumber) because InputBuffer.charCodeAt throws on out-of-bounds access rather than returning NaN.

Tests

Three new cases that previously threw are now repaired correctly, and the existing ["a" 2] / ["a" 2.5] / ["a" 2e10] regressions are verified to still pass.

✓ {"v": "包含"985/211"的候选人"}  →  {"v": "包含\"985/211\"的候选人"}
✓ {"v": "requires "2fa" enabled"}  →  {"v": "requires \"2fa\" enabled"}
✓ {"v": "version "3.0.1" released"}  →  {"v": "version \"3.0.1\" released"}
✓ ["a" 2]    →  ["a", 2]     (regression)
✓ ["a" 2.5]  →  ["a", 2.5]  (regression)
✓ ["a" 2e10] →  ["a", 2e10] (regression)

All 158 existing tests continue to pass.