v0.1.19
fix(provider): release the renderer on shutdown, and let a restart rebuild
shutdown() was a deliberate no-op, so a late-arriving handler would not meet a
torn-down proxy mid-render. That reasoning does not survive the cases it
creates: the renderer left behind holds the OLD router, the old Rosetta, the old
templates and the old ALS context, and #started then refused to build a new
one. A hot reload or a second application in the same process kept rendering
through a dead graph with nothing to say so.
The window it protected is not real in a graceful shutdown either -- in-flight
requests drain before providers are torn down. What IS real is two applications
sharing a process, which is why this clears only the instance it bound: the
survivor's renderer has to stay.
Templates still owns its own cache and AsyncLocalStorage has no destroy
contract, so neither is ours to tear down.
Changes since v0.1.18.