2.0.0-beta.15 | async read in Errored fallback does not show warning of reading without a loading boundary

[mizulu]

Describe the bug

<Errored fallback={
   asyncRead()
}>

Nothing is logged for DEV

if we read non resolved async signal in the render part of the component

<>{asyncRead()}</>

we will get the dev warning

[ASYNC_OUTSIDE_LOADING_BOUNDARY] An async value was read outside a Loading boundary. The root mount will be deferred until all pending async settles.

Your Example Website or App

https://s.olid.uk/id/UFHRJ0VYR2WaBO1FQscBJQ

Steps to Reproduce the Bug or Issue

playground

Expected behavior

It is expected that dev warning will be consistent for async signal read that is not in a Loading boundary
even though Errored does not propagate the not ready error to the Loading/Suspense boundary
it will also have the delay in rendering that is explained by the warning.

Screenshots or Videos

No response

Platform

.

Additional context

No response