release: 0.1.3

Cut as the rollback floor for store migration 9. A vault that applies
migration 9 must not be opened by v0.1.2 afterwards: that binary predates
the store-ahead refusal (landed 560073d, one day after the v0.1.2 tag) and
was measured opening a schema-ahead store and WRITING to it, so a rollback
past this release writes into a store it cannot reason about. Migration 6
rebuilt read_grants to add a NOT NULL operation column and migration 9
rebuilds it again for selector kinds, so the failure would not be a clean
refusal - it would be a write of the wrong shape.

The notes carry the two facts an operator cannot recover from the error
text. The supervisor floor: this module's manifest declares an empty
`consumes`, serde omits an empty vec, and a pre-0.17.20 daemon requires
the field, so it refuses with 'missing field consumes' - a protocol field
name for what is actually a too-old supervisor. And the placement rule:
whichever of the daemon or the CLI runs first applies migration 9, so they
move together.

Both crates bumped: the release workflow refuses a tag that disagrees with
credentials-module's version, because `ck setup` requires the tag's
version as a substring of --version and the assets would fail acceptance
on every platform.

Author: ualtinok

.github/workflows/release.yml

@@ -66,7 +66,19 @@ jobs:
           claustrum does not self-initialize. Run \`ck auth bootstrap\` before enabling
           the module, or the daemon will exit with 'no master key has been provisioned'.
           On Linux and Windows there is no keychain, so bootstrap with \`--key-path\` and
-          give the daemon the same path via CK_MASTER_KEY_PATH."
+          give the daemon the same path via CK_MASTER_KEY_PATH.
+
+          REQUIRES subc 0.17.20 OR NEWER. An older supervisor refuses this module's
+          HELLO with 'malformed HELLO body: missing field \`consumes\`' and parks it
+          after three restarts. The error names a protocol field rather than a version,
+          so it reads as a broken release; it is a supervisor that predates the field
+          becoming optional. v0.1.2 does not carry this floor.
+
+          CARRIES STORE MIGRATION 9, which rebuilds read_grants and adds credential
+          categories. Place the daemon and ck-auth TOGETHER: whichever runs first
+          migrates the store, and a v0.1.2 binary has no store-ahead refusal, so
+          rolling back past this release would write into a migrated store. This
+          release is the rollback floor for any vault that applies migration 9."
           fi
 
   assets:

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "credentials-core"
-version = "0.1.2"
+version = "0.1.3"
 edition = "2021"
 publish = false
 license = "MIT"

crates/credentials-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "credentials-module"
-version = "0.1.2"
+version = "0.1.3"
 edition = "2021"
 publish = false
 license = "MIT"