[Reiers]

Operator-ready BUILD.md, RUN-PDP.md and deploy/curio-pdp/*, rewritten from what actually worked in a 24 hour calibration run of stock Curio-PDP on bridge-off Lantern (13 consecutive proving windows per data set, every provePossession / nextProvingPeriod tx status 1, no manual intervention).

RUN-PDP.md

• "Minimum Lantern version: v1.10.1 or later" at the top.
• Flow in the order that worked: Docker + Compose >= 2.24.4 (!override), build or download Lantern (new download + sha256 snippet), init --network calibration --no-wallet with the operator-aware quorum output explained and the "daemon refuses without anchor" rule, node-type pdp, daemon as a systemd user service on the docker0 IP with --allow-remote-rpc (security and token auth), FULLNODE_API_INFO with an IP literal after /ip4/, SKIFF_HTTP_DOMAIN before first start, compose up with the three files and --no-build yugabyte skiff, migrations, GUI on 4701 via SSH, storage (100 GiB), PDP wallet, funding (5 FIL registry fee, fund >= ~6 tFIL; same in FIL on mainnet), HTTPS (Curio GUI Cloudflare tunnel step, hand-run cloudflared, or own domain/TLS), /pdp/ping, Register Provider, client data set, proving (240 epochs ~2 h on calibration).
• All TODO-VERIFY markers resolved. GUI page names taken from Curio's web UI (PDP Overview, PDP Proving, DataSets, Chain, Tasks, Storage, PDP Guide, Wallets, Configuration, PDP). Chain connection check via the Chain page.
• New "What success looks like" section (data set create processed, PDPv0_InitPP, PDPv0_Prove every period, status 1 on explorer, third-party clients, automatic termination + settlement).
• Troubleshooting rows for every error hit in the run (no contract code, unknown url scheme, DataSetCreated event not found, post-restart receipt i/o timeout, unsupported opcode 0x5e, Filecoin Pay lockup revert, quorum not reached / no trust anchor, 503 PDP wallet not configured).
• Fixed a corrupted line in the Cloudflare section on main (<tunne...Keep).

BUILD.md: TAG v1.10.1, minimum-version note, byte-for-byte check now via scripts/repro-build.sh (#174) with an explanation of why a plain go build differs.

deploy/curio-pdp: upload-test.mjs callbacks fixed against synapse-sdk 2.0.2 types (onUploadComplete does not exist, now onStored; onPiecesConfirmed takes (dataSetId, providerId, pieces)), prints Filecoin Pay balance, new EXTRA_DEPOSIT_USDFC. Status mode tested read-only against calibration; upload path tested up to the funding step with an unfunded key.

Templates: operator-report.yml and docs/VERIFICATION-M2.md now ask for hardware, OS, Lantern version + how obtained, build time, time to first proof, per-step pass/fail and friction; friction table linked to the fixing PRs.

No code changes. CGO_ENABLED=0 go build ./... passes; relative links and anchors checked.