[P2-E9.2] End-to-end acceptance scenario

**Context.** The milestone exit test, as one scripted scenario: bootstrap → register →
pay fee → vote discount → buy traffic (wallet path) → limit enforced on the dedicated
sequencer → consume → report consumption → reconciliation view squares report against
burn → fee lapses → buy blocked → arrears paid → buy restored → offboard → everything
inert.

**Deliverable.** Integration suite implementing the full arc, plus the negative
variants (unregistered buy, cross-sync fee swap, non-operator report).

**Acceptance.** Green on the two-sync LocalNet in CI; each exit criterion in
[phase-2.md](../phase-2.md) mapped to an assertion.

**Depends on.** Everything on the spine (P2-E1..E6); build incrementally as rungs land.

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

Start with docs/planning/phase-2-epics/P2-E9-testing.md and phase-2.md, then inspect the existing LocalNet integration setup and CI entry points. Build the scenario incrementally as P2-E1 through P2-E6 land, including the three negative variants. Done means the two-sync LocalNet CI run is green and every phase-2 exit criterion is covered by an assertion.

Written by the indexing model from the issue text.