Add canonical BountyVerdict agent decision tools

[Mimirs402]

Summary

Adds the canonical Mimir's Lab BountyVerdict MCP server to the Agent Finder catalog using the current direct-contribution contract.

The six existing read-only tools help agents decide whether a public GitHub bounty is worth pursuing, audit repository instructions, diagnose failed GitHub Actions runs, decide whether one retry is appropriate, and detect breaking MCP tool drift. Calls use the existing x402 USDC contracts.

This supersedes #10, whose immutable source branch references the retired personal publisher. The product behavior is unchanged; the catalog identity and source now belong to Mimirs402.

Current-schema update

• Rebased onto current catalog main after Retype plugins and unify mcp registry #12.
• Uses the documented urn:ai:github.com:<publisher>:<repo>:<augment> identifier.
• Links the public source definition at Mimirs402/bountyverdict/blob/main/server.json.
• Keeps the MCP media type and repository-owned sourceSet / repoPath metadata.
• Leads with the questions an agent would actually ask rather than internal product labels.

Verification

• The linked server.json exists on the canonical business repository and declares the production Streamable HTTP MCP remote.
• Every catalog JSON file parses.
• Catalog identifiers remain unique.
• git diff --check passes.

This requests catalog review and does not represent an impression, install, purchase, or revenue event.