types

Types shared across the keyvalue interfaces. The `bucket` resource lives here (rather than in `store`) so that every interface that operates on a bucket — `store`, `atomics`, `cas`, `batch`, `watcher` — `use`s the *same* resource type. That matters for the component-model `(implements ..)` mechanism: a host can route each labeled `store` import to a different backend, and the bucket a guest opens through one label is still accepted by the (unlabeled) `atomics`/`cas`/`batch` interfaces, because they all reference this one `types.bucket`.