Name the released specification and the released engine

openkal 0.8.0 is published and resolvable from the index, so the manifest names
it by version rather than by branch --- including the example's, where a branch
would hand a reader a reference that moves.

The engine pin moves to mcpp 2026.8.27.1 and the repository variable
MCPP_SOURCE_REF is cleared, so what this repository tests is the engine a user
installs.

Author: speak-agent

.github/workflows/ci.yml

@@ -19,7 +19,7 @@ jobs:
     runs-on: ubuntu-24.04
     timeout-minutes: 40
     env:
-      MCPP_VERSION: 2026.8.26.2
+      MCPP_VERSION: 2026.8.27.1
       XLINGS_VERSION: v2026.8.17.2
       XLINGS_NON_INTERACTIVE: '1'
       # The branch of the specification this backend is verified against. It
@@ -274,7 +274,7 @@ jobs:
       run:
         shell: bash
     env:
-      MCPP_VERSION: 2026.8.26.2
+      MCPP_VERSION: 2026.8.27.1
       XLINGS_VERSION: v2026.8.17.2
       XLINGS_NON_INTERACTIVE: '1'
     steps:

examples/hello/mcpp.toml

@@ -23,5 +23,5 @@ runner  = ["qemu-system-riscv64", "-machine", "virt", "-nographic",
 # 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 = "0.8.0"
 openkal-opensbi = { path = "../.." }

mcpp.toml

@@ -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 = { git = "https://github.com/mcpplibs/openkal", branch = "feat/openkal-0.8" }
+openkal = "0.8.0"
 
 # ⭐ WHAT RECEIVES CONTROL, WHICH IS A STATEMENT ABOUT THE PROGRAM.
 #