Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/core/utils/matching/matchRequestUrl.test.ts`:
- Around line 4-71: The test suite removed coverage for wildcard-port and
baseUrl-relative string matching; add back tests in matchRequestUrl.test.ts that
call matchRequestUrl to assert the wildcard-port pattern (e.g., matching new
URL('http://localhost:1234') against the string 'http://localhost:*' yields
matches: true, params: {}), and a test that asserts a baseUrl-relative string
pattern (e.g., matching new URL('http://example.com/base/path') against a
relative pattern like '/base/path' or a baseUrl-relative string) returns
matches: true with empty params; place these alongside the existing RegExp and
string tests using the same matchRequestUrl invocation to ensure regression
coverage for wildcard ports and base-relative string patterns.

In `@src/core/utils/matching/matchRequestUrl.ts`:
- Around line 29-38: The RegExp branch in matchRequestUrl incorrectly uses
matchAll when pattern.flags includes('g'), causing false positives and corrupted
params; change the logic to always perform a single-match with a non-global
RegExp: construct or reuse a RegExp without the 'g' flag (e.g., new
RegExp(pattern.source, pattern.flags.replace('g',''))) and call
cleanUrl.match(...) once, set matches = match != null, and build params from
(match ?? []).slice(1) as before so capture groups map correctly; remove the
matchAll/flat handling and ensure you reference the existing pattern, match,
cleanUrl, and params variables in the matchRequestUrl function.

---

Nitpick comments:
In `@src/core/utils/matching/normalizePath.ts`:
- Around line 13-21: The function normalizePath currently uses a generic <P
extends Path>(path: P): P which incorrectly promises to return the exact input
type; replace this with explicit overloads: declare normalizePath(path: RegExp,
baseUrl?: string): RegExp and normalizePath(path: string, baseUrl?: string):
string, then keep a single implementation signature normalizePath(path: Path,
baseUrl?: string): Path that performs the runtime logic (the RegExp instanceof
check, call to getAbsoluteUrl, and return cleanUrl(maybeAbsoluteUrl) as Path).
This preserves correct typing for RegExp vs string callers while keeping the
existing implementation using getAbsoluteUrl and cleanUrl.