Add Namada support to cosmos.directory (currently under _non-cosmos in chain-registry)

[maxpower-01]

Hi there
Would it be possible to include Namada in cosmos.directory?

Namada is already present in the cosmos/chain-registry.
Even though it’s located in _non-cosmos, it includes a full chain.json with relevant metadata and endpoints (e.g., apis.rpc, peers, etc.).

Question: Does the cosmos.directory intentionally exclude anything under _non-cosmos, or is there a way to opt-in chains like Namada that still provide complete chain-registry data?

Thanks!