+**Immutable.** Once a `<Loading>` has shown content it is disarmed: a later refetch or hold does not send it back to its fallback — it keeps the content, and the pending render effects under it are forwarded into the change's hold exactly as if they were read in the open (F-2). The only way back is `on` — a dependency list: a change to anything `on` reads arms the boundary again (F-4), so the render effects under it leave the hold they were forwarded into and the boundary shows its fallback, with the change's frame, until the new content is ready; if nothing under it is pending, nothing happens. One exception (D-39): behind a shown error fallback nothing is on screen, so a `<Loading>` there has not shown content — the error boundary's recovery re-arms it, and it catches what is still pending in the replacement frame as on a first load (ruled 2026-11-02, #4627). The value `on` returns is never compared, and the children are not re-created — they stay alive behind the fallback. A lane is that same hold: the async under a disarmed boundary is forwarded into it, so a display-ahead value and the content move together, exactly as they would with no boundary there.
0 commit comments