docs: fix code snippets verified against the actual z6m_prover binary

Verified every CLI claim by running `docker run somnergy/z6m_prover ...`
against `latest`. The published image is the source of truth for what
users actually see — `master` of erigontech/zilkworm has refactored some
flags/descriptions but the image hasn't been rebuilt yet, so docs should
match the image until a new image ships.

## Real bugs (fixed)

- **docs/basics/getting-started.md (CUDA example)** — `--n 1` is not a real
  flag in any version. Replace with `--block-number 1` (which the binary
  actually accepts).
- **src/pages/index.tsx (landing hero)** — `z6m_prover verify proof.json`
  would clap-error: the `verify` subcommand has no positional argument,
  only `--proof-path` (default `proof.bin`) and `--vk-path` (default
  `vk.bin`). Rewrite to `z6m_prover verify --proof-path proof.json
  --vk-path vk.bin`.
- **docs/testing/riscv-testing-eests-on-rv32im-via-qemu.md** — `make
  rv32im_eest_blockchain_tests` does not exist in `qemu_runner/Makefile`.
  The intended target is `make eest-rv32` (or `make eest-blockchain-tests`
  which defaults to `ARCH=rv32`).

## Re-verified, left as-is

The prove/execute option tables (including `--is-test` and the
"JSON file..." / "Whether the input file is..." descriptions) match the
binary verbatim — these were temporarily "corrected" against master
source in an earlier draft of this PR and have been reverted to match
what users see when they actually run `--help`.

Author: bloxster

docs/basics/getting-started.md

@@ -98,5 +98,5 @@ $ user@machine-with-gpu
 docker run --gpus all --rm --network host -v "$PWD:/work:rw" -v /var/run/docker.sock:/var/run/docker.sock  -w /work -it --entrypoint bash somnergy/z6m_prover
 
 root@instance-20250919-091229:/work# 
-SP1_PROVER=cuda RUST_BACKTRACE=full RUST_LOG=info z6m_prover prove --n 1 --file-name test.json
+SP1_PROVER=cuda RUST_BACKTRACE=full RUST_LOG=info z6m_prover prove --block-number 1 --file-name test.json
 ```

docs/testing/riscv-testing-eests-on-rv32im-via-qemu.md

@@ -54,7 +54,7 @@ git submodule foreach 'git lfs pull'
 
 ```bash
 cd zilkworm/qemu_runner
-make rv32im_eest_blockchain_tests
+make eest-rv32
 ```
 
 That would build the project for rv32im and invoke `ctest` to launch a bunch of `qemu-system-riscv32` instances in the background. Each of these instances is passed with a JSON file to run as a test.\

src/pages/index.tsx

@@ -104,7 +104,7 @@ const capabilities: Card[] = [
 
 const exampleCommand = `// Create block proofs in one command
 z6m_prover prove --block-number 23456789 --proof-path proof.json
-z6m_prover verify proof.json`;
+z6m_prover verify --proof-path proof.json --vk-path vk.bin`;
 
 export default function Home(): React.ReactElement {
   return (

static/llms-full.txt

@@ -177,7 +177,7 @@ $ user@machine-with-gpu
 docker run --gpus all --rm --network host -v "$PWD:/work:rw" -v /var/run/docker.sock:/var/run/docker.sock  -w /work -it --entrypoint bash somnergy/z6m_prover
 
 root@instance-20250919-091229:/work# 
-SP1_PROVER=cuda RUST_BACKTRACE=full RUST_LOG=info z6m_prover prove --n 1 --file-name test.json
+SP1_PROVER=cuda RUST_BACKTRACE=full RUST_LOG=info z6m_prover prove --block-number 1 --file-name test.json
 ```
 
 ---
@@ -388,7 +388,7 @@ git submodule foreach 'git lfs pull'
 
 ```bash
 cd zilkworm/qemu_runner
-make rv32im_eest_blockchain_tests
+make eest-rv32
 ```
 
 That would build the project for rv32im and invoke `ctest` to launch a bunch of `qemu-system-riscv32` instances in the background. Each of these instances is passed with a JSON file to run as a test.\