fix: display non-string query parameters in resource registry

[craigbidenbot]

Summary

Number and boolean query params (like page and include_gt_community_data) were silently dropped from the Resource Registry display. Only string-typed schema values were handled.

Changes

• schema.ts: Handle typeof raw === 'number' and typeof raw === 'boolean' in expandFields, inferring type as integer/number or boolean respectively, with defaults pre-filled
• form/index.tsx: Add queryFields to targetUrl dependency array so typed query values serialize correctly into the URL

Test Plan

• View a resource with mixed query param types (e.g. CoinGecko trending pools with page=1, duration=5m, include_gt_community_data=true, include=base_token)
• Verify all 4 params now appear in the form
• Verify integer/boolean params serialize correctly when executing the request

Closes #623

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
x402scan	Ready	Preview, Comment	Mar 13, 2026 10:46pm

[vercel]

Additional Suggestion:

isValidFieldValue function doesn't validate type-specific constraints, allowing invalid numbers in required fields to pass validation but get silently dropped during serialization

[fmhall]

We've since removed the ResourceExecutor and its display code entirely in favor of a simpler "Copy Prompt" flow that directs users to test endpoints via agentcash.dev. The query parameter rendering this fixed no longer exists. Closing as obsolete.