examples: name openkal the way this repository does

mcpp refuses a graph in which one package reaches a dependency by version and
another by git:

    dependency 'mcpplibs.openkal' is requested as both a version dep (by 'hello')
    and a git dep (by 'mcpplibs.openkal-<this>@path'). Pick one.

That is the right refusal --- two forms can name two different trees --- and it
means an example inside a repository must follow that repository's own
declaration while a change spanning repositories is in flight. The example named
a released version while the package beside it followed a branch.

Author: speak-agent

examples/hello/mcpp.toml

@@ -13,5 +13,15 @@ runner  = ["qemu-system-riscv64", "-machine", "virt", "-nographic",
            "-no-reboot", "-bios", "default", "-kernel"]
 
 [dependencies]
-openkal = "0.7.0"
+# ⚠️ THE FORM MUST MATCH THE ONE THE IMPLEMENTATION USES, not merely the
+# version. mcpp refuses a graph in which one package reaches a dependency by
+# version and another by git:
+#
+#     dependency 'mcpplibs.openkal' is requested as both a version dep
+#     (by 'hello') and a git dep (by 'mcpplibs.openkal-opensbi@path').
+#
+# That is the right refusal --- two forms can name two different trees --- and
+# it means an example inside a repository follows that repository's own
+# declaration while a change is in flight.
+openkal = { git = "https://github.com/mcpplibs/openkal", branch = "feat/openkal-0.8" }
 openkal-opensbi = { path = "../.." }