Pre-install canonical-identity verification

genesis_pin and verify_candidate both relate to canonical verification, but genesis_pin's description ('PINNABLE only for a verifying CANONICAL receipt') is nearly incomprehensible, making it unclear when to use it versus the main verify tool. get_receipt is distinct, but overall boundaries between the other two are fuzzy.

Two tools follow verb_noun (get_receipt, verify_candidate) while genesis_pin uses a noun_pin pattern, breaking consistency. The mixed convention reduces predictability and forces the agent to infer each tool's action.

Three tools is a thin surface for a verification service; while not extreme, it feels insufficient for managing receipts or plans, and genesis_pin's unclear role doesn't clearly earn its place.

There is no tool to list receipts, manage plans or payments, or batch verify; the workflow from verification to receipt retrieval is possible but lacks lifecycle coverage. genesis_pin's ambiguous purpose suggests missing context or incomplete design.