release-publish-prep: package metadata landed on the four published crates (descriptions, keywords, categories; family precedent — no homepage/docs fields); ADR-017 §1 pre-release class-1 amendment — initial release 0.1.0 (user decision, family 0.x-initial precedent, manifest pins ride the §4.1 pre-1.0 0.y form)

docs/architecture/decisions/017-contract-versioning.md

@@ -92,6 +92,21 @@ Concretely:
   ([ADR-008](008-contract-v1-pinning.md)) — is a content
   designation, not yet a semver claim.
 
+**Pre-release amendment (class-1 event, 2026-10-11 — the window this
+release itself closes):** the initial release is **0.1.0**, decided
+with the user at `tasks/release-publish-prep.md` — the family's
+0.x-initial precedent carried over (alkcall 0.8.1, alktunnels 0.2.1,
+alksocks 0.1.0, alkblobs 0.1.0), and the paragraph above's 1.0.0 pin
+explicitly superseded. What stands unchanged: contract v1's content
+ships whole in 0.1.0 (the class-1-window termination still lands
+exactly here, not at 1.0); the §4.1 manifest pins take the ADR's own
+pre-1.0 `0.y` form (`alkstore = { version = "0.1", path = … }`); and
+Cargo's 0.x semantics govern — a contract breaking change bumps `0.y`,
+additions bump `0.y.z` (§2's classes, unchanged). The full coupling
+binds at the future 1.0: from that release, contract major ⇔ crate
+major, and the change history remains traceable through the core
+crate's changelog.
+
 ### 2. The event taxonomy: four classes of contract change
 
 Every change to the contract text is exactly one of these, and