Public setup-readiness notes for MCP/x402 discovery surfaces

[maxim-ultra]

Hi ForgeMesh team,

I reviewed the public repo because it is directly in the MCP/x402 discovery lane and noticed a few setup-readiness gaps that may matter for developers and agents trying to validate the ecosystem surfaces from scratch.

Public evidence from the repo:

• README.md explains the registry, MCP packages, x402 challenge flow, and discovery files
• site/public/index.json, llms.txt, and openapi.json are present
• package.json and site/package.json exist, but the top-level README does not make the exact install/build/test path obvious
• I could not find a root AGENTS.md, CONTRIBUTING.md, .env.example, or a short troubleshooting section for common discovery/setup failures

Small checklist that would make the repo easier to validate:

• add the exact root and site/ commands a new contributor should run
• document whether npm install, npm run build, and npm run dev are expected at root, site/, or both
• add a safe .env.example if any local site variables are expected
• add AGENTS.md with stack, commands, safe edit areas, and verification expectations for coding agents
• add a short troubleshooting note for discovery files and hosted endpoint drift

No private repo access, credentials, account access, or local machine context is needed. This is only a public-readiness note from the visible repository files.