Constant KERNEL_HELP_NO_RAW 

pub const KERNEL_HELP_NO_RAW: &str = "Kernel identifier: a source directory \
     path (e.g. `../linux`), a version (`6.14.2`, or major.minor prefix \
     `6.14` for latest patch), a cache key (see `kernel list`), a \
     version range (`6.12..6.14`), or a git source \
     (`git+URL#tag=NAME`, `git+URL#branch=NAME`, or `git+URL#sha=<40-hex>`). Raw \
     image files are rejected. Source directories auto-build (can be slow \
     on a fresh tree); versions auto-download from kernel.org on cache \
     miss. The flag is REPEATABLE on `test`, `coverage`, and `llvm-cov` \
     — passing multiple `--kernel` flags fans the gauntlet across every \
     resolved kernel; each (test × scenario × topology × kernel) \
     tuple becomes a distinct nextest test case so nextest's parallelism, \
     retries, and `-E` filtering work natively. Ranges expand to every \
     `stable` and `longterm` release inside `[START, END]` inclusive \
     (mainline / linux-next dropped). Git sources are fetched at the \
     given ref (GitHub via a codeload snapshot, other hosts via a \
     shallow clone) and built once. In contrast, `ktstr shell` accepts a single \
     kernel only — pass exactly one `--kernel`.";

Help text for --kernel in contexts that reject raw image files: cargo ktstr test, cargo ktstr coverage, cargo ktstr llvm-cov, and ktstr shell. Matches KernelResolvePolicy { accept_raw_image: false, .. }.

Raw images are rejected here because these commands depend on a matching vmlinux and the cached kconfig fragment alongside the image (test/coverage need BTF, ktstr shell reuses the cache entry for kconfig discovery). A bare bzImage/Image passed directly carries neither, so silently accepting it would produce hard-to-diagnose mid-run failures. cargo ktstr shell accepts raw images because its flow does not need that companion metadata; see KERNEL_HELP_RAW_OK.