fix(examples): 09 names the cuRAND and CCCL payloads the clang route needs (#567)

* fix(examples): 09 names the cuRAND payload the clang route needs

clang's CUDA wrapper includes curand_mtgp32_kernel.h unconditionally; the
example built on a developer machine only because the host's /usr/include
supplied it. mcpp.rules.cuda 0.1.0 refuses the clang route without
xim:libcurand and names the entry; the example now declares it.

* fix(examples): 09 also names the CCCL payload

cuRAND's header includes <nv/target> from CCCL, the separate cuda-cccl
package of the 12.x toolkits; the host's /usr/include supplied it silently
on the developer machine. mcpp.rules.cuda refuses the clang route without
it and names the entry; the example declares 12.9.27, the 12.9 line.

* ci: re-run checks on the amended head

---------

Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>

Author: Sunrisepeak

examples/09-cuda-kernel/app/mcpp.toml

@@ -40,6 +40,13 @@ cuda-runtime = "2026.09.05"
 [xlings.workspace]
 "xim:cuda-nvcc"         = "12.9.86"
 "xim:cuda-cudart"       = "12.9.79"
+# cuRAND's headers and CCCL. clang's CUDA wrapper includes
+# curand_mtgp32_kernel.h for every device unit, and that header includes
+# <nv/target> from CCCL, so the clang route needs both even though this kernel
+# calls neither; on a developer machine the host's /usr/include used to supply
+# them silently. 10.3.x and 12.9.27 are the 12.9 line.
+"xim:libcurand"         = "10.3.10.19"
+"xim:cuda-cccl"         = "12.9.27"
 "xim:libcuda-host-link" = { linux = "0.0.1" }
 
 [build]