Draft: refresh SDK and daemon docs for current setup, retrieval, and storage flow

[JimCollinson]

Summary

• refresh daemon setup, run-as-daemon, and mainnet guidance for the current direct-wallet and external-signer configuration
• update the REST, gRPC, MCP, and JavaScript SDK reference pages for current upload response fields, payment_vault_address, and daemon timeout/concurrency flags
• restructure the SDK and daemon getting-started flow so readers can start antd read-only, retrieve existing data from the network first, then branch into default-network writes, external signers, or a local devnet
• add a dedicated Retrieve Data from the Network Getting Started page and wire it into navigation and the deeper read-only guide
• rename the onboarding pages and cross-links so the sequence now reads cleanly as Build with the SDKs -> Start the Local Daemon -> Retrieve Data from the Network -> Store Data on the Network -> Use the CLI -> Build Directly in Rust
• update embed-a-node.md, manage-keys.md, and related guides to match the current ant-node crate release and CLI usage

Why

Recent merged ant-sdk, ant-client, and ant-node changes moved these docs out of sync around payment vault configuration, upload result models, daemon runtime options, and the practical onboarding flow for the SDK route. This draft PR brings the technical details back in line with merged truth and makes the first-run daemon path progress from health check to retrieval before upload payment choices, without inventing an install path that does not exist yet.

Source Refs

• ant-sdk: bf541ccd4ae1fd3e174fb7b5bb21deef38d999ce
• ant-client: eb29e99937b1aedba02db04e1ae59bd923b424a3
• ant-node: d3f5ba969b8ccf98ca0c50b661a3762aec904634

Review Focus

• confirm EVM_PAYMENT_VAULT_ADDRESS now replaces the older daemon payment env names everywhere this batch touches
• confirm file and directory upload responses plus prepare and finalize examples match the current REST, gRPC, and MCP behavior
• confirm the ant-node crate version, custom EVM note, and ant CLI invocation examples reflect the merged source-of-truth behavior
• confirm the getting-started flow now separates source-build requirements from optional upload configuration, exposes a clear read-only retrieval branch, and uses clearer page titles and link labels throughout the onboarding sequence

[JimCollinson]

@claude Please review this draft PR against current merged truth in ant-sdk, ant-client, and ant-node.
Focus on:

• factual accuracy of the docs changes
• incorrect or stale env var names, field names, commands, or examples
• missing doc updates that should have been included in this batch
• whether any changed verification blocks look wrong or incomplete
  Please pay particular attention to:
• EVM_PAYMENT_VAULT_ADDRESS replacing older daemon payment env names
• REST, gRPC, and MCP upload response fields
• external-signer prepare/finalize flow, including payment_type, payment_vault_address, tx_hashes, and winner_pool_hash
• ant CLI invocation examples and flag ordering
• embed-a-node.md guidance, including the ant-node crate version and custom EVM config note
  Please give findings first, with file paths and line references where possible. If you find no issues, say that explicitly and mention any residual risks or gaps.

[claude]

Claude encountered an error —— View job

---

PR Review in Progress

• Read all 12 changed files
• Check git diff against origin/main
• Verify EVM_PAYMENT_VAULT_ADDRESS usage across changed files
• Verify REST, gRPC, MCP upload response fields
• Verify external-signer prepare/finalize flow fields
• Verify ant CLI invocation examples and flag ordering
• Verify embed-a-node.md crate version and EVM config note
• Check verification blocks for correctness
• Compile findings and post review