v0.3.1

Internal only. No API, behavior, or documentation changes; safe to take from 0.3.0 without reading further.

Changed

ContextFrame keeps one representation for its bindings (#28, follows #25/#26)

0.3.0 stored a frame with a single binding in a dedicated key/value object instead of a Map. Measured on its own, that saved 20–40 ns per Job — under 3% of a Job and invisible end to end — and left two representations behind every frame that from, with, and withEntries had to keep in step. It is reverted; a frame is a Map again.

The consumer that created a one-binding frame per request (the HTTP server binding ContainerKey) now hosts its DI scope on the Runner attachment and creates no per-request frame at all (@tiberjs/di ScopeHost), so the one-binding case is no longer on any hot path.