Docs/UX: clarify discovery filters, reputation, and channel-history thresholds

[alogotron]

Summary

Clarify when providers may be hidden or de-prioritized by network/desktop discovery filters such as reputation, activity, or channel-history thresholds.

Problem

A new provider can be technically live and discoverable through direct CLI/DHT lookup while still being hard to find in desktop/network discovery if filters are enabled.

This can confuse both buyers and providers:

• provider is seeding,
• direct peer lookup works,
• metadata endpoint works,
• but desktop discovery does not show it,
• users assume the provider is offline or invalid.

Suggested UI/docs copy

Some filters may hide new providers until they build channel history or reputation.
If you know the provider peer ID, use direct peer lookup or lower the discovery filters.

Suggested CLI examples

# Direct peer lookup
antseed network peer <peer-id>

# Service discovery by exact service key
antseed network browse --service <service-key> --json | jq

Filter explanations to expose

• minimum channel history,
• minimum reputation/trust score,
• active-only filter,
• service/tag filters,
• price filters,
• provider-level vs service-level stats.

Why this matters

Reputation filtering is important for buyer safety, especially as AntSeed moves toward trust-weighted routing. But legitimate new providers need a clear path to be found without resorting to spammy or synthetic channel activity.