Missing dev warning for repeated forward slashes in an href

[AhmedElBanna80]

Found running the official Next.js e2e test suite against vinext (vinext 1.0.0-beta.8, Next.js 16.2). Error line is from the suite's own output.

Fixture: test/e2e/repeated-forward-slashes-error

Symptom: the Invalid href development warning is never emitted; the test times out waiting for it. Low priority (dev-only parity).

Repro: render a link whose href has repeated slashes in dev mode; expect the Invalid href warning.

[AhmedElBanna80]

Update: this appears already addressed on current main — the Invalid href dev warning is implemented and invoked on Link render, with a passing test. Reported against 1.0.0-beta.8; will confirm on the next published release. Close at your discretion.