[Low] --timeframe help text is incomplete — API accepts 10m but it is not listed

[Nicolai1205]

Summary

The --timeframe help text lists 5m 1h 6h 24h 7d 30d as valid values, but the API also accepts 10m. This was discovered from the API error message when passing an invalid timeframe.

Discovery

nansen research token screener --chain solana --timeframe 2h

The API error message listed valid timeframes including 10m:
Valid values: 5m, 10m, 1h, 6h, 24h, 7d, 30d

But the CLI help text shows only:
Valid values: 5m, 1h, 6h, 24h, 7d, 30d

Impact

Low. 10m granularity is useful for short-term analysis. Users and agents following only the help text would not know it exists.

Fix

Add 10m to the timeframe enum in the schema and all help text that lists valid timeframe values.

Found during

Clawfooding session on v1.10.1. Referenced in PR #167.