docs: fix code snippets to match actual zilkworm source

Cross-repo audit against erigontech/zilkworm@master surfaced 6 drifts
where docs claimed CLI flags / Make targets / help text that don't
exist in the actual source. Fixes (all against prover_hypercube/src/main.rs
unless noted):

1. getting-started.md — `prove` options table: drop the bogus `--is-test`
   row (flag only exists in commented-out prover_turbo) and rewrite
   `--block-number` + `--file-name` descriptions to match source ("Block
   number to prove" / "Path to the unified RLP input file (overrides
   --block-number lookup)").

2. getting-started.md — `execute` options table: same fixes as #1.

3. getting-started.md — CUDA example: `--n 1` is not a real flag (it was
   a leftover from before z6m_prover existed). Replace with the canonical
   `--block-number 1`.

4. src/pages/index.tsx (landing hero) — `z6m_prover verify proof.json`
   would fail with a clap parse error. The `verify` subcommand requires
   named flags only: `--proof-path <PATH>` and `--vk-path <PATH>`. Update
   the hero example accordingly.

5. riscv-testing-eests-on-rv32im-via-qemu.md — `make rv32im_eest_blockchain_tests`
   target does not exist in qemu_runner/Makefile. The intended target is
   `make eest-rv32` (or `make eest-blockchain-tests`, which defaults to
   ARCH=rv32). Switch to `eest-rv32`.

Regenerated llms-full.txt so the inline copies of the affected pages
stay in sync.

Author: bloxster

docs/basics/getting-started.md

@@ -66,8 +66,7 @@ Usage: z6m_prover execute [OPTIONS]
 
 Options:
       --block-number <BLOCK_NUMBER>  Block number to execute [default: 0]
-      --file-name <FILE_NAME>        Whether the input file is an Ethereum/tests file
-      --is-test                      
+      --file-name <FILE_NAME>        Path to the unified RLP input file (overrides --block-number lookup)
       --data-dir <DATA_DIR>          Data directory
   -h, --help                         Print help
 
@@ -78,9 +77,8 @@ Options:
 ```text
 Usage: z6m_prover prove [OPTIONS]
 Options:
-      --block-number <BLOCK_NUMBER>  JSON file to load ethereum/tests format test from [default: 0]
-      --file-name <FILE_NAME>        Whether the input file is an Ethereum/tests file
-      --is-test                      
+      --block-number <BLOCK_NUMBER>  Block number to prove [default: 0]
+      --file-name <FILE_NAME>        Path to the unified RLP input file (overrides --block-number lookup)
       --data-dir <DATA_DIR>          Data directory
       --pk-path <PK_PATH>            Proving key path [default: pk.bin]
       --proof-path <PROOF_PATH>      Proof output path
@@ -98,5 +96,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

@@ -145,8 +145,7 @@ Usage: z6m_prover execute [OPTIONS]
 
 Options:
       --block-number <BLOCK_NUMBER>  Block number to execute [default: 0]
-      --file-name <FILE_NAME>        Whether the input file is an Ethereum/tests file
-      --is-test                      
+      --file-name <FILE_NAME>        Path to the unified RLP input file (overrides --block-number lookup)
       --data-dir <DATA_DIR>          Data directory
   -h, --help                         Print help
 
@@ -157,9 +156,8 @@ Options:
 ```text
 Usage: z6m_prover prove [OPTIONS]
 Options:
-      --block-number <BLOCK_NUMBER>  JSON file to load ethereum/tests format test from [default: 0]
-      --file-name <FILE_NAME>        Whether the input file is an Ethereum/tests file
-      --is-test                      
+      --block-number <BLOCK_NUMBER>  Block number to prove [default: 0]
+      --file-name <FILE_NAME>        Path to the unified RLP input file (overrides --block-number lookup)
       --data-dir <DATA_DIR>          Data directory
       --pk-path <PK_PATH>            Proving key path [default: pk.bin]
       --proof-path <PROOF_PATH>      Proof output path
@@ -177,7 +175,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 +386,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.\