0.6.0 --- follow openkal 0.12 (#15)

No behaviour changes. The specification's 0.12 additions are prose: clause 11
entry 9 names what handles-do-not-cross costs a caller composing job control,
and the two file-creating operations point at entry 6.

The bump exists because a version requirement here is exact --- nothing floats
up --- so a specification release moves the whole graph or nothing resolves.

Author: Sunrisepeak

mcpp.toml

@@ -14,7 +14,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-opensbi"
-version     = "0.5.0"
+version     = "0.6.0"
 description = "An implementation of openkal on the RISC-V Supervisor Binary Interface, portable across every machine whose firmware provides one"
 license     = "Apache-2.0"
 
@@ -33,7 +33,7 @@ repo        = "https://github.com/mcpplibs/openkal-opensbi"
 # The contract, not an implementation of it. Declaring it turns a version
 # mismatch into a resolution-time message rather than a link-time one.
 [dependencies]
-openkal = "0.11.0"
+openkal = "0.12.0"
 
 # ⭐ WHAT RECEIVES CONTROL, WHICH IS A STATEMENT ABOUT THE PROGRAM.
 #