docs: drop io-dir layout and logging sections from --help

Keep the CLI help focused on options and usage examples; the io-dir layout
and startup/logging behaviour are covered in the README and docs/. The
README usage block is regenerated to match the trimmed --help output.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: RaoulSchaffranek

README.md

@@ -80,26 +80,6 @@ options:
   --io-dir IO_DIR  directory for all input/output artifacts (default: a fresh
                    temporary directory)
 
-io-dir layout:
-  All input and output lives in the io-dir. With --io-dir omitted, a fresh
-  temporary directory is used, so each launch starts from an empty chain and
-  leaves the working directory untouched.
-
-    state.kore     the world state
-    metadata.json  the ledger counter
-    receipts/      one receipt file per transaction
-    traces/        one execution trace per transaction
-    requests/      an archive of each request
-
-  Each transaction and request gets its own file, so nothing grows without
-  bound. Point --io-dir at the same directory on the next launch to resume the
-  same chain, or at an empty directory to start over.
-
-logging:
-  On startup the server logs, to stderr, the io-dir path, the address it is
-  listening on, and whether it is starting fresh or resuming an existing chain.
-  Every incoming request is logged to stderr as well.
-
 examples:
   komet-node                     serve on localhost:8000 in a fresh temp dir
   komet-node --port 9000         use a custom port

src/komet_node/__main__.py

@@ -10,26 +10,6 @@
 _DESCRIPTION = 'Komet Node — a local Stellar testnet backed by the K semantics of Soroban.'
 
 _EPILOG = """\
-io-dir layout:
-  All input and output lives in the io-dir. With --io-dir omitted, a fresh
-  temporary directory is used, so each launch starts from an empty chain and
-  leaves the working directory untouched.
-
-    state.kore     the world state
-    metadata.json  the ledger counter
-    receipts/      one receipt file per transaction
-    traces/        one execution trace per transaction
-    requests/      an archive of each request
-
-  Each transaction and request gets its own file, so nothing grows without
-  bound. Point --io-dir at the same directory on the next launch to resume the
-  same chain, or at an empty directory to start over.
-
-logging:
-  On startup the server logs, to stderr, the io-dir path, the address it is
-  listening on, and whether it is starting fresh or resuming an existing chain.
-  Every incoming request is logged to stderr as well.
-
 examples:
   komet-node                     serve on localhost:8000 in a fresh temp dir
   komet-node --port 9000         use a custom port