Agent Registry: add optional verification block to the Concordium Badge

[MarirosansP]

What

Adds an optional verification block to the Concordium Badge's concordium card block, plus a short "Zero-setup path" note in Resolve and verify a badge. Additive only.

Why

Today the badge tells a consumer what to check (the verify string) but not where. A party with no prior Concordium tooling has no machine-readable pointer to a node, Indexer, or MCP endpoint, so it cannot bootstrap verification from the card alone — defeating the point of an agent discovering a badge it has never seen before.

The verification block closes that gap: a first-time consumer can GET the verifyUrl and read the verdict, or point an MCP client at mcp and call verify_agent_card / agent_by_token_address directly.

Trust model unchanged

Every field is a discovery convenience, not an authority. The trust root remains the on-chain contracts named in contracts; a consumer may ignore the hints and resolve directly against the chain (the existing steps). A named resolver returns chain-derived data the consumer can re-check.

Compatibility

Purely additive and optional — badges without verification stay valid. No page is added or renamed, so the landing-page document map and public/llms.txt are unaffected.

Fields added: service, verifyUrl (single-GET REST verdict), mcp (MCP endpoint), indexer, docs.

🤖 Generated with Claude Code