docs(wallet-cli): 从 wallet-cli 仓库命令文档

[jizhen181-dot]

将 tronprotocol/wallet-cli 仓库自带的用户文档（origin/develop @ 0190dab7） 完整迁移为中文，与英文源一一对应，共 153 篇：

index.md ← README.md
java/index.md ← java/README.md
java/{guide,concepts,commands,reference}/ 25 篇
typescript/index.md ← ts/README.md
typescript/{guide,concepts}/ 11 篇
typescript/commands/ 112 篇（20 个子目录）
typescript/{machine-interface,troubleshooting}.md

替换原有 12 篇手工合并的页面（java-cli.md、typescript-cli.md、
wallet-management.md 等），mkdocs.yml 导航整段重写。

其中 16 处技术表述与实际实现不符，已按源码修正（confirmed 表示已入块
而非已固化、not_found 超时属状态未知、--sign-only 仍需联网、--dry-run 仍调用 RPC、密码要求的例外、轮询脚本的退出码处理、tx broadcast 的
Synopsis、argv/环境变量措辞），依据均可在 ts/src 中核对。

[vivian1912]

This PR ultimately synchronizes wallet-cli documentation from feat/v4.13.0 @ cc19d485, not from develop; the earlier develop @ 0190dab7 import was superseded by the later sync commit. However, cc19d485 is an intermediate snapshot: the current release_v4.13.0 head is 82486420, 67 commits ahead, including user-visible CLI contract and documentation fixes such as EVM tx sign --out support and error-contract updates.
In addition, the latest package currently published on npm is still v4.12.0, while these pages describe unreleased v4.13-only functionality such as EVM support. Please synchronize from the final v4.13 release source and either coordinate publication of these pages with the v4.13 package release or clearly version/label them as unreleased. Otherwise, the main documentation site will describe commands that the install instructions do not provide, while also retaining behavior that is already stale relative to the release branch.

[jizhen181-dot]

Thanks for the review — all four points were valid. Each was verified against the wallet-cli sources rather than taken on faith, and all are now fixed.

1. Cross-implementation derivation. Confirmed. ts/src/domain/family/index.ts sets indexAt: "account" (m/44'/195'/'/0/0), while SubAccount.java builds PATH_PREFIX + first + "'/0/" + second and defaults to incrementing the last segment (m/44'/195'/0'/0/i). Only account 0 matches. The claim that both derive the same accounts is removed; the page now states that the account stores are not interchangeable, gives both path templates, notes that a wallet restored in the other CLI shows different addresses rather than missing funds, and tells the reader to check the recorded BIP44 path before migrating.

2. ./gradlew directory. Confirmed — the Gradle project is java/; there is no wrapper at the repo root. Fixed to cd wallet-cli/java && ./gradlew build && cd build/libs, both in the code block and in the install row of the comparison table.

3. RegisterWallet. Confirmed — Client.registerWallet() takes no argument; it calls inputPassword2Twice(false) and then asks for the mnemonic length, so extra parameters are ignored. Fixed to bare RegisterWallet, annotated that it prompts twice for the password and then for the mnemonic length.

Points 2 and 3 were flagged on index.md; the same two defects were present in java/index.md, so both files are fixed, in the English and Chinese trees.

4. Sync source and release timing. Both concerns are resolved. The branch is re-synced from develop @ 3960316e (release_v4.13.0 merged), which contains 82486420 and the follow-ups you named — EVM tx sign --out, the error-contract changes (errorCodes exit/retry metadata, ambiguous_account), idempotent import keystore, and the broadened invalid_node_response. On publication timing: @tron-walletcli/wallet-cli@4.13.0 was published to npm on 2026-09-04T12:07Z, about eight hours after your comment, and is now dist-tags.latest. The install instructions and the documented feature set therefore agree, so no "unreleased" labelling is needed.

[jizhen181-dot]

All three confirmed and fixed.

1. Duplicate account-creation paragraph in java/guide/getting-started.md. You're right — I corrected commands/account.md last round and did not sweep for the same claim elsewhere. The paragraph now defers to that page instead of restating a number: it says an activation fee is burned and bandwidth is consumed, that both are governance-controlled chain parameters rather than fixed amounts, and links to commands/account.md#how-to-create-account.

2. Duplicated migration_required. Removed. The exit-2 table listed it twice; the shorter of the two entries is dropped, and the one that explains the master-password condition is kept. Both trees now list it once.

3. Dead mechanism-algorithm/dex.md link. Confirmed — the file was removed upstream in 5fcebec Remove obsolete documentation files, and mechanism-algorithm/ on master no longer contains it. I checked whether the link could be repointed instead: system-contracts.md has sections for the Exchange contracts, but they are protobuf field listings and do not explain the Bancor pricing the sentence refers to. So the link is removed and the Bancor statement kept, as you suggested.

This one is worth calling out as a process gap on my side rather than a one-off. The link resolved fine against this branch, whose base still carries dex.md, so every link check I ran passed; it only breaks once the target branch is merged. I've added validation of cross-tree links against upstream/master — the only other two, mechanism-algorithm/resource.md and using_javatron/installing_javatron.md, both survive there, so this was the only occurrence.

I also swept for siblings of 1 and 2 rather than fixing just the reported instances: no other table in either tree repeats a row key, and the remaining 1 TRX / 0.1 TRX occurrences are unit definitions (1 TRX = 1,000,000 SUN) or console output samples, not rules stated as fixed amounts.