Decentralized Dispute Loop and Peer Auditing

Description:
Create the feedback mechanism where Consumer Edges can audit Producer Edges to prevent "Fake" compliance receipts.

Requirements:

Dispute Signals: If a Consumer Edge detects a violation missed by the Producer, it generates a signed "Dispute Receipt."
Quorum Consensus: If N independent consumer edges (with high hardware attestation scores) dispute a post, trigger an automatic "Quarantine" on-chain.
Appeal Agent: An arkavo-edge role that re-evaluates disputed content using a "Heavier" LLM model or human-in-the-loop signal.

The issue names no files, tests, or entry points. Start by locating the existing receipt, edge-role, and on-chain quarantine paths, then determine where dispute signals, quorum decisions, and appeal handling belong. Done requires an agreed design and tests covering the stated dispute, quarantine, and appeal requirements.

Written by the indexing model from the issue text.