0.5.1 --- the runner over openkal-macos 0.22.1, and the kernel layer as compatible ranges

README.md

@@ -22,6 +22,11 @@ its generated surface and image calling convention. The runner selects Linux
 missing native identity remains `unknown`. The format and the existing import
 names remain unchanged.
 
+Version 0.5.1 builds the runner over openkal-macos 0.22.1, whose confinement
+rules hold sixteen long grants, and states the kernel layer as compatible ranges
+(openkal `^0.24.0`, Linux `^0.25.0`, macOS `^0.22.1`, Windows `^0.20.0`). The
+format, the loader and the import names are unchanged.
+
 ## An image
 
 ```sh

bind/mcpp.toml

@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-bind"
-version     = "0.5.0"
+version     = "0.5.1"
 # `mcpp::xpkg_request', `mcpp::decision' (protocol 15).
 mcpp        = ">=2026.10.1.3"
 description = "A build plugin: a library published as an ok image (.okso) and a C header is called from a program of any system, through a binding generated from the header and libokrun."

docs/bind.md

@@ -109,6 +109,7 @@ llvm toolchain's clang converts the call.
 | 0.3.1 | No change of its own; released with the archive, whose runner admits a remembered okb member by its shape without reading it. |
 | 0.3.2 | No change of its own; released with the archive, whose runner is built over openkal 0.22's implementations: a started program is given the system's null device at a position (`KAL_SPAWN_NULL_*`). |
 | 0.5.0 | The binding format is unchanged; the runner selects OpenKal 0.24 and binds its four process-unit operations. |
+| 0.5.1 | No change of its own; released with the archive, whose runner is built over openkal-macos 0.22.1 (confinement rules sized to their grants). |
 | 0.4.0 | No change of its own; released with the archive, whose loader places an image at the base `okld place` chose for it (openkal 0.23, `kal_exec_alloc_at`) and then applies only the relocations that name a symbol. |
 | 0.4.1 | No change of its own; released with the archive, whose runner on macOS is built over openkal-macos 0.21.2 (a sleep is no longer a spin of the processor; the granularity is the same at every start). |
 | 0.4.2 | No change of its own; released with the archive, whose runner on macOS is built over openkal-macos 0.21.3 (asked before the implementation's initialiser ran, it answers from the loader's record). |

ld/mcpp.toml

@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-ld"
-version     = "0.5.0"
+version     = "0.5.1"
 description = "libokld: the ok format (openkal image format) --- its definition, a reader of bytes, a checker, a signer, and a loader. Freestanding: no C library, no exceptions."
 license     = "Apache-2.0"
 authors     = ["mcpplibs"]

run/mcpp.toml

@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-run"
-version     = "0.5.0"
+version     = "0.5.1"
 description = "libokrun: the runner's core --- an ok image's names bound to this process's one openkal implementation, in the image's calling convention, and its entry entered."
 license     = "Apache-2.0"
 authors     = ["mcpplibs"]
@@ -11,17 +11,17 @@ repo        = "https://github.com/mcpplibs/openkal-image"
 kind = "lib"
 
 [dependencies]
-openkal = "0.24.0"
+openkal = "^0.24.0"
 openkal-ld = { path = "../ld" }
 
 [target.linux.dependencies]
-openkal-linux = "0.25.0"
+openkal-linux = "^0.25.0"
 
 [target.macos.dependencies]
-openkal-macos = "0.22.0"
+openkal-macos = "^0.22.1"
 
 [target.windows.dependencies]
-openkal-windows = "0.20.0"
+openkal-windows = "^0.20.0"
 
 # The interfaces each system's implementation provides decide one unit: where
 # openkal.space is provided its names are bound, and elsewhere an image that

tools/mcpp.toml

@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-tools"
-version     = "0.5.0"
+version     = "0.5.1"
 description = "okrun, which runs an ok image on this system, and okld, the format's tool on a build machine (check, note, sign, inspect)."
 license     = "Apache-2.0"
 authors     = ["mcpplibs"]