Missing dev warning for repeated forward slashes in an href

_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.

Start with the `test/e2e/repeated-forward-slashes-error` fixture and run the relevant official Next.js e2e test to reproduce the timeout. Trace the development-mode handling of a link href containing repeated slashes. Done means the `Invalid href` development warning is emitted and the fixture completes successfully.

Written by the indexing model from the issue text.