alkstore 0.1.0

The alkstore contract crate: one reactive store trait surface — notify, streams, durable queues, TTL locks, outbox, scheduler — implemented by the alkstore-sqlite/-postgres/-mem engine crates; no driver dependencies
Documentation
# alkstore

The core crate of the [alkstore](https://git.alk.dev/alkdev/alkstore/blob/main/README.md)
family: the contract artifact — the unified `Store` trait surface,
value types, error taxonomy, and the naming / reserved-namespace
contract of the reactive store substrate. It has no driver
dependencies, ever (payload encoding's `serde`/`serde_json` are its
only dependencies); engine crates depend on it and implement its
traits.

Downstream consumers depend on `alkstore` plus exactly one engine
crate: [`alkstore-sqlite`](https://crates.io/crates/alkstore-sqlite),
[`alkstore-postgres`](https://crates.io/crates/alkstore-postgres), or
[`alkstore-mem`](https://crates.io/crates/alkstore-mem). Engine
identity is compile-time — the engine crate your binary depends on
*is* the deployment statement; there is no runtime capability surface.

See the [family README](https://git.alk.dev/alkdev/alkstore/blob/main/README.md)
for the interface, the engine postures, and the deployment matrix;
the crate's own docs are part of the contract.