register-ai-agentlisted

# Register AI Agent Register only the current missing agent. Never guess another provider's account or use another provider's bot. The registry review is the trust boundary. ## Discover and verify 1. Search official provider documentation, official repositories, and GitHub for the agent's canonical co-author identity. 2. Require evidence that the exact email resolves to the expected provider-controlled account: - A numeric `users.noreply.github.com` address must contain the matching GitHub account ID and login. - A provider-domain address needs a public proof commit where GitHub's rendered author mapping links that email to the expected account. 3. Verify the candidate programmatically: ```bash node <skill-dir>/scripts/verify-coauthor.mjs \ --agent <agent> \ --label '<display label>' \ --github-login '<login>' \ --email '<email>' \ [--proof-commit '<github-commit-url>'] ``` The command exits `0` only when the identity resolves to the expected GitHub account. It emits a registry-ready verified entry and stores rendered proof hashes in validated fragments so secret scanners do not mistake public commit IDs for credentials. ## Update the registry 1. On successful verification, add the emitted entry to the sibling `attribute-ai-commits/references/providers.json` registry. 2. If diligent official-source research finds no valid identity, add an `unavailable` entry with `aliases`, `status`, `reason`, `evidence`, and `