[P2-E6.3] Reconciliation view: reported consumption vs settled burn

**Context.** The report is only useful if someone compares it to burn. Phase 2 requires
the comparison to be *available* (audit view), with automated SV-side alerting as
stretch: consumed-to-date vs purchased-to-date per synchronizer, flagged when consumption
exceeds purchases beyond tolerance.

**Deliverable.** Scan (or SV app) view joining report history against summed
registered-sync purchases per synchronizer; discrepancy metric; documentation of the
governance response path (offboard vote, FR-2).

**Acceptance.** LocalNet: consume, report, view shows reconciled totals; synthetic
over-consumption shows a discrepancy.

**Depends on.** P2-E6.1, P2-E7.2.

**Refs.** FR-27, FR-28, FR-2.

—
Epic: #69 · Plan: [P2-E6-consumption-reporting.md](https://github.com/ChainSafe/canton-extending-mainnet/blob/main/docs/planning/phase-2-epics/P2-E6-consumption-reporting.md)

Read docs/planning/phase-2-epics/P2-E6-consumption-reporting.md and review the work from P2-E6.1 and P2-E7.2 before locating the Scan or SV app reconciliation entry point. Implement the audit view joining report history with registered-sync purchases per synchronizer, then verify the LocalNet and synthetic over-consumption acceptance cases.

Written by the indexing model from the issue text.