docs: make the CLI the source of truth for ferro-vm commands

명령 목록이 tools/README.md와 argparse 정의 두 곳에 손으로 동기화되고 있었다.
드리프트가 불가피하므로 목록을 --help로 단일화한다.

cli.py에 서브커맨드별 help/description, 인자 metavar, 예시 epilog를 채웠다.
put의 DOS 8.3 이름 제약처럼 명령에 직접 붙는 함정은 해당 도움말에 넣었다.
tools/README.md는 호스트 요구사항, 셋업, 자동화 구조로 줄이고 목록은 --help로
넘긴다. AGENTS.md에는 CLI가 규범이라는 포인터를 남긴다.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012PQm6oAvWX4Lp3iSN5AHGT

tools/README.md

@@ -6,46 +6,41 @@ Automation currently supports **Windows 10/11 only**. It requires `uv`, QEMU
 with WHPX support, and `ffmpeg.exe` on `PATH`. The Python implementation uses
 portable APIs where possible, but other hosts are not supported yet.
 
-## QEMU and FreeDOS automation
-
-Start the Python daemon and QEMU:
+## Getting started
 
 ```powershell
 uv run ferro-vm start
 uv run ferro-vm status
 ```
 
-`TCPAGENT.EXE` connects only to `127.0.0.1:5558`. Local commands use the
-Windows named pipe `\\.\pipe\ferrolang-vm`; there is no controller or observer
-TCP port. Monitor the append-only structured log in another terminal:
+The command list lives in the CLI itself, not in this file:
 
 ```powershell
-uv run ferro-vm logs
+uv run ferro-vm --help
+uv run ferro-vm <command> --help
 ```
 
-Commands:
+Working rules, verification gates, and DOS build traps are in `AGENTS.md`.
 
-```powershell
-uv run ferro-vm reset       # clean QEMU quit and restart
-uv run ferro-vm wait-ready --timeout 45
-uv run ferro-vm ping
-uv run ferro-vm exec 'dir C:\FEC'
-uv run ferro-vm put fec/src/check.c 'C:\FEC\SRC\CHECK.C'
-uv run ferro-vm get 'C:\FEC\TEST.OK' .qemu/TEST.OK
-uv run ferro-vm screenshot
-uv run ferro-vm ocr
-uv run ferro-vm stop
-```
+## How it fits together
 
-`reset` cleanly quits and restarts QEMU, waits for FreeDOS to boot, submits
-the default boot-menu Enter, and requires TCPAGENT `PING`/`PONG`. QEMU
-`system_reset` is intentionally unsupported because repeated soft resets leave
-the FreeDOS NE2000 packet driver stuck during initialization. `logs` starts
-`lnav` when installed and otherwise falls back to PowerShell `Get-Content
--Wait`. The daemon logs command metadata, DOS output, exit status, transfers,
-and agent lifecycle events as UTF-8 lines. It deliberately never logs raw binary
+`TCPAGENT.EXE` runs inside FreeDOS and dials out to `127.0.0.1:5558`; its wire
+protocol is documented in `tcpagent/README.md`. The `ferro-vm` daemon owns that
+connection and the QEMU monitor. Local commands reach the daemon over the
+Windows named pipe `\\.\pipe\ferrolang-vm` — there is no controller or observer
+TCP port.
+
+The daemon writes an append-only structured log (`uv run ferro-vm logs`, which
+uses `lnav` when installed and otherwise falls back to PowerShell `Get-Content
+-Wait`). It records command metadata, DOS output, exit status, transfers, and
+agent lifecycle events as UTF-8 lines, and deliberately never logs raw binary
 payloads or protocol hex.
 
+`reset` quits QEMU cleanly, restarts it, waits for FreeDOS to boot, submits the
+default boot-menu Enter, and requires a TCPAGENT `PING`/`PONG` before returning.
+QEMU `system_reset` is intentionally unsupported: repeated soft resets leave the
+FreeDOS NE2000 packet driver stuck during initialization.
+
 ## Standalone OCR
 
 `tools/qemu_ocr.py` remains available for OCRing an existing image: