{% comment %}
SPEC §5's four counters as headline cards, for the flow stats page.

The broadcast page deliberately does not include this: its figures come from
`broadcast.stats` via `apps.broadcasts.services.counters` and mean something
narrower — one send's recipients rather than a node's lifetime — so sharing the
markup would have implied a shared definition that does not exist.

`clicked` carries clicks-per-send beneath it wherever there were sends to divide
by — "where buttons exist" in the issue's words, expressed as "where anything was
counted" so a flow whose only link is inside an email body reads the same as one
with a button.

It is labelled a ratio rather than a rate, and can legitimately read over 100%:
`clicked` counts clicks while `sent` counts messages, and SPEC §18 keeps no
per-contact history, so one recipient pressing a link three times is three.
{% endcomment %}
<div class="an-cards">
    <div class="an-card">
        <div class="an-card-figure">{{ totals.sent }}</div>
        <div class="an-card-label">Sent</div>
    </div>
    <div class="an-card">
        <div class="an-card-figure">{{ totals.delivered }}</div>
        <div class="an-card-label">Delivered</div>
    </div>
    <div class="an-card">
        <div class="an-card-figure">{{ totals.failed }}</div>
        <div class="an-card-label">Failed</div>
    </div>
    <div class="an-card">
        <div class="an-card-figure">{{ totals.clicked }}</div>
        <div class="an-card-label">Clicked</div>
        {% if click_rate is not None %}<div class="an-card-note">{{ click_rate }}% clicks per send</div>{% endif %}
    </div>
</div>