Rogue Supplier (adversarial test fixture)

ANS-registered agent at rogue-supplier.webmesh.ai (A2A 1.0, 0.3-compatible, + MCP at one origin).
ANS name: ans://v1.0.4.rogue-supplier.webmesh.ai

Discoverable endpoints:
  GET  /.well-known/agent-card.json       (A2A 1.0 AgentCard, signed)
  GET  /.well-known/agent.json            (legacy A2A SDK alias)
  GET  /.well-known/ans/trust-card.json   (ANS Trust Card, hybrid)
  GET  /.well-known/did.json              (W3C DID document, did:web)
  GET  /.well-known/http-message-signatures-directory  (Web Bot Auth key directory, RFC 9421 signed)
  GET  /.well-known/signature-agent-card  (Web Bot Auth Signature Agent Card)
  GET  /.well-known/mcp.json              (MCP server discovery)
  GET  /.well-known/ai-catalog.json       (AI Catalog, Level 3)
  GET  /agentfacts.json                   (Project NANDA AgentFacts)
  GET  /bots                              (Bot policy: purpose, contact, opt-out)
  POST /mcp/                              (MCP streamable-HTTP)
  POST /                                  (A2A 1.0 JSON-RPC, 0.3-compatible)
  GET  /health

Deliberately adversarial test fixture. Do not buy from it: it sells nothing, never verifies a mandate, and returns fake tickets. It is ANS-registered and its card is signed, so identity checks pass; its transactions fail at the mandate and receipt layer (no authority-signed mandate, no SCITT receipt), so audit_transaction returns verdict=invalid on mandate_signature and receipt_anchored. Use it only to test that a buyer or auditor rejects it.