Migrate Local Node content to Solo ahead of September 2026 deprecation

## Background

Hiero Local Node deprecates **September 2026** ([blog](https://hedera.com/blog/hiero-local-node-deprecation-6-month-transition-to-solo/)). A first pass landed **#463** (the `` snippet) and **#671** (Solo call-outs).

With Local Node deprecating, its content should come out of hedera-docs and be replaced with Solo as *the* local network, rather than staying in as annotated/deprecated material. A single deprecation banner should live on the Local Development landing page — nowhere else.

## A. Anchor the section

- [ ] **A1. Create `native/local-dev/index.mdx`.** No index page exists today — which is why `/native/local-dev` redirects to `setup-local-node` (`docs.json` ~line 141), landing readers on the Local Node walkthrough. One page solves both problems: Solo-first landing content for the Local Development section, hosts the **single** `` banner, and removes the `/native/local-dev` redirect so the URL resolves to the real page (the legacy `/hedera/tutorials/local-node` redirect at ~line 1946 then chains here correctly).
- [ ] **A2. Add Solo to the `docs.json` navigation.** `docs.json` contains zero occurrences of "Solo" (`grep -ci solo docs.json` → `0`) across 3,453 lines. The "Local Development" group (~line 2777) lists only `setup-local-node`, `setup-cli-npm`, and `cde/`; the "Localnet" group (~line 2282) is the same. Add the new index page plus a Solo entry at the top of the group, and drop retired pages (C1, C2) as they go.
- [ ] **A3. Update the `skill.md` network table.** Line 154 reads `| localnet | Local testing (via Hiero Local Node) | Auto-funded | Ephemeral |` — the only local-network guidance in the agent-facing file, with no Solo mention anywhere in it. Change the row to Solo and add a gotcha for Solo's ports. Fold into the [#732](https://github.com/hashgraph/hedera-docs/issues/732) AI work.

## B. Convert pages to Solo

For each: rewrite the Local Node instructions as Solo instructions, then remove the `` import and banner where present.

- [ ] **B1. `evm/tools/hardhat/index.mdx`** — Trim and defer *(decided)*. Solo's `using-solo-with-evm-tools.md` is already a full Hardhat-on-Solo walkthrough — deploy, ECDSA accounts, `hardhat.config.ts`, contract deploy, ethers.js, MetaMask, teardown, troubleshooting. Don't rebuild it here. Cut this page to a short intro (what the relay is, why Hardhat needs ECDSA keys, Hedera-specific gotchas) and link out for the walkthrough. Removes most of the page, including the Local Node setup steps.
- [ ] **B2. `evm/tools/foundry/setup.mdx`** — Rewrite in place. Solo has **no** Foundry guide, so unlike B1 this page isn't trimmed to a link — "Option A: Run Hedera Localnet" gets replaced with Solo network-setup instructions written out here. The Foundry-specific content (`foundry.toml`, `forge script`/`cast`, Sourcify verification) stays. Update the remaining endpoints and keys to Solo. Ask the Solo team whether they'd rather own a Foundry guide upstream; if they do, this page trims to a link like B1 once that guide exists.
- [ ] **B3. `evm/development/json-rpc/index.mdx`** — Replace the "Hiero Local Node" relay option (option 1 in prose and in the comparison table) with Solo. Link `using-solo-with-evm-tools` and `endpoints`.
- [ ] **B4. `native/fundamentals/local-network.mdx`** — Delete the "Local Node (deprecated)" section and its Java/JS/Go samples; keep and expand the Solo section so the code samples use Solo endpoints.
- [ ] **B5. `networks/localnet/index.mdx`** — Delete the "Local Node (deprecated)" section and the Local Node entries under "Additional Resources." The Solo half is already the best in the repo and stays as-is.
- [ ] **B6. `native/local-dev/setup-cli-npm.mdx`** — Repoint the Hedera CLI setup at a Solo network.
- [ ] **B7. `solutions/tools/hiero-cli/overview.mdx`** — Replace the three "Hedera Local Node" prerequisite/localnet references with Solo. Verify the CLI works against Solo — its `network.config.ts` defaults assume Local Node's ports.
- [ ] **B8. `native/index.mdx`** — Replace the "Local Node" card in the "Local development" grid with a Solo card; drop the Gitpod/Codespaces cards when those pages retire (C1).
- [ ] **B9. Four quickstarts** — Move the Solo `` to the top of the page: `native/quickstart/javascript.mdx` (line 110 of 132), `java.mdx` (130/152), `go.mdx` (119/141), `evm/quickstart/get-test-hbar.mdx` (101/107). All currently place it after the reader has committed to the testnet path; the four EVM deploy quickstarts already do this right at lines 11–13.

## C. Retire

- [ ] **C1. `native/local-dev/cde/{gitpod,codespaces,index}.mdx`** *(decided)* — Solo doesn't run in Gitpod — the `kind`/Kubernetes requirement doesn't fit, unlike Local Node's Docker Compose setup. There's no Solo replacement to write, so these retire rather than convert. Also drop their links from `networks/localnet/index.mdx`, their cards from `native/index.mdx` (B8), their nav entries (A2), and the `gitpod/` + `codespaces/` image directories.
- [ ] **C2. `native/local-dev/setup-local-node.mdx`, `networks/localnet/single-node.mdx`, `networks/localnet/multinode.mdx`** — These exist only to document Local Node; converting them would just duplicate Solo's own quickstart. Retire and redirect to the new Local Development index (A1) or to Solo's quickstart. Open question: retire as B completes, or freeze them until the Sept 2026 cutoff? Nothing links to them once B is done.
- [ ] **C3. `snippets/local-node-deprecation.mdx`** — Down to one usage after B — keep it for A1, or inline the warning there and delete the snippet.