[ColinkaMir]

Closes #116

Change

handleSlash gets an nfts case:

• /nfts sends { action: "get_nfts" } and /nfts <address> sends { action: "get_nfts", address }, both through handleAction. Everything runAction already does applies unchanged:
  • the active account when no address is given;
  • the address refusals, including the checksum one from fix: refuse bad address checksum on read actions instead of throwing #114;
  • the indexer and network refusals from fetchReservoir;
  • the existing list format and page limit.
• More than one argument prints usage: /nfts [address] and fails a scripted run, the same way /history and /send handle bad arity.
• /help and the header comment in cli.mjs list the command. The README command list includes it, and the sentence that said NFT reads need the model now covers only token sends and NFT transfers.

No new read path, no change to NFT formatting or pagination, nothing on the transfer side.

Verified

test/nfts-command.test.mjs runs the built CLI (dist/cli.mjs) in scripted mode with the existing @qvac/sdk shim, so processLine → handleSlash → handleAction is the real path. The indexer is a loopback server that records which owner it was asked about.

Six cases:

• Default account. Asserts the indexer was asked about the address /address printed in the same run, and that the existing list format comes back.
• Explicit owner. The indexer is asked about exactly that owner.
• Malformed address. Refused, no indexer read, exit 1.
• Extra arguments. Usage line, no indexer read, exit 1.
• No indexer for the network. Mainnet with no RESERVOIR_API_URL shows the refusal, exit 1.
• /help. It lists the command.

The model is never called. The shim gains an opt-in call log (NAD_SHIM_CALL_LOG), and every /nfts case asserts it stayed empty.

Red, then green:

• On main. All six fail for the expected reasons: unknown command: /nfts, no indexer read, exit 0 where 1 is expected.
• Mutations. Dropping the scripted failure on extra arguments fails the extra-arguments case. Ignoring the explicit address fails the explicit-owner and malformed-address cases.
• Full suite. npm run build && npm test: 552/552 on Node 22.23 (CI's major version) and on Node 20. The new file was rerun twice with no flakes.

[portdeveloper]

looks good, thanks