Problem
gpu-denied.yml (the CI job that should assert GPU-less/CPU-only behavior) bans the CPU-only kernels crate outright rather than exercising it, so the workflow cannot actually verify CPU-only correctness for that crate.
Impact
There is no CI coverage proving the kernels crate's CPU-only path works, in a workflow specifically meant to guard that path — the same "source-only review, never hardware/path-qualified" shape the week's synthesis names for kernel lanes generally (E.10).
Fix
Adjust gpu-denied.yml's allow/deny rule so the CPU-only kernels crate is included and exercised under the GPU-denied condition instead of excluded.
Evidence: sessions s61, s78
Problem
gpu-denied.yml(the CI job that should assert GPU-less/CPU-only behavior) bans the CPU-onlykernelscrate outright rather than exercising it, so the workflow cannot actually verify CPU-only correctness for that crate.Impact
There is no CI coverage proving the
kernelscrate's CPU-only path works, in a workflow specifically meant to guard that path — the same "source-only review, never hardware/path-qualified" shape the week's synthesis names for kernel lanes generally (E.10).Fix
Adjust
gpu-denied.yml's allow/deny rule so the CPU-onlykernelscrate is included and exercised under the GPU-denied condition instead of excluded.Evidence: sessions s61, s78