fix(regex): include the empty string when a zero-min quantifier applies to a number pattern

[spokodev]

Fixes #1625

Problem

regex("(\\d*)") types the capture group as `${number}`, which excludes the empty string even though * matches zero repetitions. ? has the same problem (regex("(\\d?)") → `${number}`).

The tryFastPath branch in ark/regex/quantify.ts returns early for number-like patterns on the premise that repeating `${number}` does not change the type — true for one or more repetitions, but zero repetitions produce "", which `${number}` does not include. The early return runs before the min extends 0 handling, so every zero-min quantifier (*, ?, {0,n}) over a number pattern drops the empty branch. The string fast path is unaffected because string already contains "".

Fix

Make the number fast path min-aware: zero-min quantifiers produce "" | ${number}`` and quantifiers withmin >= 1keep the existing ``${number}` `` result.

Tests

Two type-level tests (* and ? over \d in a capture group) fail on main with

+ 'Regex<`${number}`, { captures: [`${number}`]; }>'
- 'Regex<`${number}` | "", { captures: [`${number}` | ""]; }>'

and pass with this change. Full mocha run: 1766 passing; the 2 failures in ark/attest/__tests__/snapPopulation.test.ts reproduce identically on a clean checkout of main and are unrelated. Prettier and ESLint clean on the changed files.

[pullfrog]

✅ No new issues found.

Reviewed changes — fix for regex zero-min quantifier incorrectly narrowing number patterns to exclude the empty string.

• Make tryFastPath in quantify.ts min-aware for number patterns — when a zero-min quantifier (*, ?, {0,n}) applies to a `${number}` pattern, the result now includes "" | `${number}` instead of just `${number}`.
• Add type-level tests for * and ? over \d in a capture group.

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) ｜ 𝕏}

[ssalbdivad]

Great, thanks!