Fia Signals showcase merged; request ACP/Butler discovery-index review for agent 18788

[Odds7]

Fia Signals (virtualAgentId: 18788) is registered, online, and publicly packaged in this repository, but remains weakly discoverable for the buyer intents its live offers serve.

Public packaging:

• Showcase: showcase/fia-signals-safe-swap-preflight/
• Merged PR: safe_swap_preflight distribution test packet #56
• Merged at: 2026-07-21T07:13:08Z
• Merge head SHA: 2c3587305f06675f20d23a5b6beb37a930a9c766

Live seller/payment surface:

• Agent: Fia Signals
• Virtual agent ID: 18788
• Live route: https://x402.fiasignals.com/token-safety/lite
• The unpaid route returns a valid 402 Payment Required with x402 v2 payment instructions and Bazaar discovery metadata.

Fresh ACP discovery readback on 27 July 2026:

• safe swap preflight: Fia rank 29
• token safety: Fia rank 38
• Base/rugpull/honeypot buyer wording: Fia rank 37
• exact Fia Signals: Fia rank 46

Could the Virtuals support/indexing team please confirm:

1. whether merged acp-cli-demos showcases are expected to feed ACP/Butler discovery;
2. whether agent 18788 and its current job descriptions are present in the production discovery index;
3. whether any hidden/restricted/graduation/index state is suppressing this agent from buyer-intent results; and
4. whether an index refresh or another builder-side action is required.

This is a discovery/indexing request only. The seller runtime and unpaid payment challenge are healthy, but no external paid conversion is being claimed.

[Odds7]

Approved builder update for agent 18788: at 2026-07-27T03:21:24Z we changed the production ACP profile description to lead with safe_swap_preflight, the $0.01 Base token-swap safety gate, and exact buyer-intent terms (token_swap, guarded swap, honeypot, rugpull, before funds move). Immediate post-change hybrid browse readback still shows Fia Signals at rank 17 for “safe swap preflight”, rank 39 for “Base token swap safety”, and rank 36 for “honeypot rugpull before token swap”. Could a maintainer confirm whether this profile update should trigger automatic production reindexing, or whether agent 18788 needs a manual refresh or another builder-side action?