v0.0.2 — the kernel, and the binary that needed it

v0.0.2 — the kernel, and the binary that needed it

Six crates: the five from 0.0.1 plus gwk-kernel.

This is the version where cargo install gridwork started working, exactly as
the 0.0.1 README said it would — publishing the kernel is what changed. What
you get is the headless CLI; it still needs a PostgreSQL 16 and two separate
database roles before it does anything.

The kernel is a daemon owning an append-only event store as the sole writer,
projections written in the same transaction as their events, content-addressed
encrypted blobs, authority evaluation that leaves a receipt, and a framed
protocol over a Unix socket. Certified against a real PostgreSQL 16 including
crash, race, and process-boundary cases.

Still pre-1.0: schemas, protocols, and the binary change without notice.

Tagged retroactively. This tag names the commit the registry was published
from, which is why it carries no release engineering of its own.

v0.0.1 — the contract crates

v0.0.1 — the contract crates

Five crates to crates.io under Apache-2.0: gwk-domain, gwk-cert, gwk-theme,
gridwork, and gwk.

cargo install gridwork did NOT work at this version, and the README said so
at the time: the gw binary and the gwk-kernel behind it were in the tree and
not on the registry. What shipped here is the contract — domain types, event
schemas, four state machines with their edge tables, the pure transition
function, the storage port and its conformance suite, and gwk-cert, which
replays an exported event stream against the contract.

Tagged retroactively. This tag names the commit the registry was published
from, which is why it carries no release engineering of its own.