Add evm collectibles command for NFT listings with spam filtering

[ivpusic]

• GET /v1/evm/collectibles/{address} with --chain-ids, --filter-spam, --show-spam-scores, --limit, --offset
• Text table shows CHAIN, NAME, SYMBOL, TOKEN_ID, STANDARD, BALANCE plus SPAM/SPAM_SCORE when --show-spam-scores is set
• Full OpenAPI spec coverage including metadata, spam explanations with json.RawMessage for polymorphic values
• 6 E2E tests: text, JSON, filter-spam disabled, spam scores JSON, spam scores text columns, pagination

[ivpusic]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add svm transactions command with signature extraction and block time formatting #39
• Add svm balances command with SimClient wiring #38
• Add evm defi-positions command for DeFi portfolio positions #37
• Add evm token-holders command with token address as positional arg #36
• Add evm token-info command for token metadata and pricing #35
• Add evm collectibles command for NFT listings with spam filtering #34 👈 (View in Graphite)
• Add evm transactions command and fix OpenAPI spec gaps across all EVM commands #33
• EVM activity #31
• Sim evm stablecoins #30
• Get balance #29
• Sim evm balances #28
• Supported chains #27
• Sim auth #26
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Low Risk
Low risk: this is an additive CLI subcommand that calls a new API endpoint and formats output, with no changes to existing query flows besides command registration.

Overview
Adds a new sim evm collectibles <address> command that calls GET /v1/evm/collectibles/{address} with flags for --chain-ids, --filter-spam, --show-spam-scores, --limit, and --offset.

Supports both raw JSON output and a text table view, optionally adding SPAM/SPAM_SCORE columns and printing next_offset for pagination, and wires the new subcommand into the sim evm command tree.

Adds E2E tests covering text vs JSON output, spam filtering toggle, spam score inclusion, and pagination via next_offset.

^{Written by Cursor Bugbot for commit 8a633b2. Configure here.}

[cursor]

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

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Attribute value typed as string, not RawMessage
  • Changed collectibleAttribute.Value from string to json.RawMessage to properly handle polymorphic NFT attribute values (strings, numbers, booleans) consistent with the codebase pattern.

Or push these changes by commenting:

@cursor push 9d59d3b559

Preview (9d59d3b559)

diff --git a/cmd/sim/evm/collectibles.go b/cmd/sim/evm/collectibles.go
--- a/cmd/sim/evm/collectibles.go
+++ b/cmd/sim/evm/collectibles.go
@@ -69,9 +69,9 @@
 }
 
 type collectibleAttribute struct {
-	Key    string `json:"key"`
-	Value  string `json:"value"`
-	Format string `json:"format,omitempty"`
+	Key    string          `json:"key"`
+	Value  json.RawMessage `json:"value"`
+	Format string          `json:"format,omitempty"`
 }
 
 type spamExplanation struct {

Comment @cursor review or bugbot run to trigger another review on this PR

[cursor]

Attribute value typed as string, not RawMessage

Medium Severity

collectibleAttribute.Value is typed as string, but NFT metadata attribute values are commonly polymorphic (strings, numbers, booleans). The codebase consistently uses json.RawMessage for polymorphic API values — spamExplanation.Value in the same file and functionInput.Value in activity.go both do this. If the API returns a non-string attribute value, json.Unmarshal in the text-output path will fail, breaking the entire command for any NFT with numeric traits.