docs(test): describe Genesis runtime and dialog checks

xCAT-test/native/README.md

@@ -138,6 +138,10 @@ permissions and an init process that reaps orphaned children.
 evaluate machine and package policy, install local-file recipes into temporary
 directories, generate extension manifests and reject invalid extension
 metadata. It does not extract or evaluate recipe source fragments.
+The POWER patch case keeps BitBake's machine prepends and replaces only the
+upstream kernel task body with a no-op. It applies the real patch to a small
+metadata fixture, checks repeat runs and verifies that patch errors propagate.
+It does not run the complete upstream kernel configuration task.
 
 For example, from the source checkout:
 
@@ -160,6 +164,17 @@ ppc64, ppc64le, armv7hf, aarch64, riscv64 and s390x.
 console with Meson, then runs the installed program. It requires a C compiler,
 Meson, Ninja, pkg-config, and development packages for Newt and systemd.
 
+`python3 xCAT-test/native/genesis_console_dialogs.py` needs the same build
+dependencies plus the `pyte` Python package. It runs the linked console in a
+pseudo-terminal and checks help and diagnostics navigation, scrolling and
+return to the main screen. It checks termination from the main screen, not
+from inside a dialog.
+
+The Genesis runtime BATS cases need Bash, Perl, OpenSSL, coreutils, diffutils
+and bubblewrap. The credential-file cases use a private `/etc` in a Linux
+namespace. The credential-file case fails if bubblewrap or user namespaces
+are unavailable; it does not skip.
+
 The unit test retains checks of the vendored release key, requested kernel
 fragments and console service configuration. The BATS tests retain runtime,
 console, hardware and packet behavior. None of these checks replaces a full