docs: Announce Nano (XNO) availability across documentation and templates

[cbrunnkvist]

I was a bit too focused on the technical side in #109, and left out a fair chunk of "end-user discoverability" by failing to mention the chain in all (more than I expected) the different places where we mention builtin support for x y and z.

This PR ensures that Nano/XNO/nano_ are consistently listed alongside other supported chains, what standard derivation paths are used, etc. There are also some code samples updated accordingly...

Mostly, I found mentions in...:

• per-language README.md files
• chain summary tables here and there
• examples and "Usage:" references
• TypeScript and Python code sample output
• the quickstart snippets and getting started guides now mention Nano as part of the default supported chains
• Crate-level files also reflect Nano support

In short, we ensure that developers, users and Googlebots alike can discover that Nano is now a supported chain in the OWS ecosystem 👍

Testing

• cargo test --workspace passes
• cargo clippy --workspace -- -D warnings is clean
• npm test passes (if Node bindings changed)
• Tested manually with ows CLI

Notes

There is already a companion-utility that bundles a set of Nano-transacting Agent skills 🦀 at @casualsecurityinc/xno-skills now built directly on top of the OWS 🥳 (but I think it is outside of the scope of these OWS documents to mention 3rd party tooling in the docs)

---

Note

Low Risk
Markdown-only discoverability updates with no runtime, signing, or policy behavior changes.

Overview
Documentation-only follow-up so Nano (XNO) shows up everywhere other built-in chains are advertised, after the implementation landed elsewhere.

Nano is added to supported-chain tables and narrative lists (Ed25519, nano_ addresses, m/44'/165'/0') in the root and binding READMEs, readme/partials/supported-chains.md, and docs/07-supported-chains.md—including CAIP-2 nano:mainnet, the nano CLI alias, and HD derivation in the mnemonic tree. Quickstart and SDK sample comments now name Nano (and NEAR/Spark where lists were tightened) so default wallet creation is described consistently.

^{Reviewed by Cursor Bugbot for commit b9f8f68. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

@cbrunnkvist is attempting to deploy a commit to the MoonPay Team on Vercel.

A member of the Team first needs to authorize it.

[cbrunnkvist]

Uh, also please let me know if completely overlooked how perhaps some docs-amending agent maybe is supposed do do this authoring in some semi-auto fashion?! I.e. am I even doing the right thing here?

[0xultravioleta]

Hey @cbrunnkvist, you're doing the right thing here. These docs are hand-authored, there's no auto-generation step you missed, so writing them out like this is exactly what's wanted.

Two practical things. First, this branch has a conflict with main now, so it needs a rebase. Second, since these docs announce Nano as available, they should land right after the signing work in #217 rather than ahead of it, otherwise the docs describe something that isn't in main yet. So let's keep this one just behind #217: get that in, rebase this, and it merges right after.

Thanks for splitting the docs out into their own PR, it makes both easier to review.

[cbrunnkvist]

Rebased onto latest upstream/main and resolved all merge conflicts from #221 (NEAR chain support). All 14 conflicted files now include both Nano and NEAR entries.

This PR is ready to merge once #217 (Nano signing implementation) lands.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 2f1704d. Configure here.}

[cbrunnkvist]

😅 oops, fixed