From 8de84f62ae9c00247fb9d6a4492b8baa7f589103 Mon Sep 17 00:00:00 2001 From: calic Date: Thu, 6 Aug 2026 11:27:20 +0200 Subject: [PATCH] fix(deps): cascade composition 0.4.0 + crafting 0.5.0 pins Phase J (2026-08-03) bumped lib-core.composition 0.3.0->0.4.0 and lib-core.crafting 0.3.0->0.5.0, but only vagrant-skeleton and lib-core.crafting themselves were updated. Dependent manifests kept the old pins, so dep-fetcher saw disagreeing pins on the same lib and refused to start both spine-prototype (ENGINE_ERR_LIB_DEP_MISSING, rc=19) and vagrant-skeleton ("dep check failed", conflict on lib-core.composition + lib-core.crafting). Unify all pins on the on-disk versions. No code changes required: composition 0.4.0 is purely additive (the quality/condition loud-error was removed; no signature changed), and crafting-display only consumes crafting.can_craft + crafting.list_recipes, both still present, and never referenced the `form` field retired by ADR-0055. README "Requires:" lines synced to match the manifests (Gate 3). milestone-check.sh: GREEN (build, ctest, smoke, devwrap-ci, test-all-modules + anomaly scan). vagrant-skeleton headless run clean at 60 CI frames. Co-Authored-By: Claude Opus 5 (1M context) --- manifest.lib | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manifest.lib b/manifest.lib index 4ebf5b7..5f8d63e 100644 --- a/manifest.lib +++ b/manifest.lib @@ -1 +1 @@ -{"id":"lib-core.actor","version":"0.1.0","api_min":"0.1","deps":[{"id":"lib-core.composition","version":"0.3.0"}]} +{"id":"lib-core.actor","version":"0.1.0","api_min":"0.1","deps":[{"id":"lib-core.composition","version":"0.4.0"}]}