feat(web): report request failures met before any render - #3763

Summary

Closes #3723.

A failure that fails a request before any render or server function met it (a Start middleware throw, a setup or renderMode module failing) had no public way to reach the server error hook. solidjs/solid-vite-plugin#383 reports it today through reportServerError from solid-js/internal, labelled kind: "render" because ServerErrorSite.kind had nothing else, and repeats failRender's console.error fallback by reading the hook slot off globalThis.

• reportRequestFailure(error, event) in the server entry of @solidjs/web, next to configureServerErrors: it reports { kind: "request", handling: "failed", event } through reportServerError, then calls console.error(error) only when no ambient hook is registered, the same policy as failRender. The hook's return is ignored, as for every handling: "failed", and the once-per-error ledger applies, so a direct server-function failure already heard as server-function/thrown isn't heard again when it escapes the middleware.
• "request" added to ServerErrorSite.kind in solid-js, on both the server and the client declaration.
• A no-op reportRequestFailure in server-mock.ts, as configureServerErrors has, so the client entry exports it too.

I exported it from the package root rather than @solidjs/web/server, which the issue mentions: the package has no ./server subpath today, and configureServerErrors already lives in the root's server build.

How did you test this change?

Five tests in packages/web/test/server/server-error-hook.spec.tsx:

• the ambient hook hears one request/failed call carrying the event, its return is ignored, and nothing reaches console.error;
• the same error object reported twice is heard once;
• a direct server-function call that throws under a request and escapes to the handler is heard once, as server-function/thrown with direct: true, and reportRequestFailure adds no second call;
• with no hook the failure reaches console.error;
• a throwing hook is reported on the console and the call returns normally.

They fail on next, where the export doesn't exist.

pnpm build, then:

Public API changes

• New reportRequestFailure(error: unknown, event: RequestEvent): void from @solidjs/web (server entry; a no-op on the client).

• ServerErrorSite.kind (and so ServerErrorContext.kind) gains "request", always with handling: "failed" and event set.

• Behavior change: the server error hook (the render's onError, or the ambient configureServerErrors hook) now hears { kind: "render", handling: "failed" } for a synchronous throw out of renderToString or out of renderToStream's first pass (and so renderToFrameStream and serverComponentResponse), before the error is rethrown to the caller. Previously these reached the caller without the hook hearing them. A handler that catches the rethrow and calls reportRequestFailure adds nothing (once per error). With no hook, nothing is logged on this road; the rethrow is the caller's. Added by the maintainer on this branch.

Maintainer changes

• Merged next (with chore(size): keep the size comparison green on fork PRs #3765) into this branch; .github/workflows/size.yml now matches next, replacing this PR's duplicate change.
• Synchronous render throws reported as render/failed before rethrow, with tests (renderToString, renderToStream, renderToFrameStream, per-render onError, no-hook case, and a genuine pre-render failure still reporting request).
• "request" documented as a failure that fails the request outside any render or server function the runtime reports.
• server: renderToString floor cap raised 20.38 → 20.42 KB (+35 B), ledger note in scripts/size/scenarios.js.

Size-Exception: renderToString reports synchronous render throws as render/failed before rethrowing (+35 B), accepted by the maintainer.