{# Executive — Probes tab compact table (QA-032 / QA-049 / BUG-1 / per-agent
   grouping 2026-06-03).

   A 5-column scannable table:

     AGENT · ASI  |  VERDICT  |  TURNS  |  LAST ACTIVITY  |  (row opens modal)

   One ROW PER AGENT (operator feedback 2026-06-03)
   -----------------------------------------------
   Recon alone emits ~17 individual turn records; rendering one row per turn
   buried the conversation. Each row now represents ONE AGENT's whole probe
   run — its ordered turns are collapsed into a single conversational entry
   (:func:`_assemble_probe_groups`). Clicking the row opens the shared modal
   (``_slideover.html``) with that agent's full turn-by-turn chat plus the
   final judge reasoning.

   Row activation
   --------------
   Each row carries:

     * ``data-action="probe-row-click"`` — the row-click contract the
       shared slide-over JS (``executive_findings.js``) keys off (QA-049).
       Click + Enter/Space open the modal.
     * ``data-source="probe"`` — selects the probe renderer in JS.
     * ``data-probe-href="/scan/<id>/probe?group=<agent>"`` — the URL the
       drawer JS ``fetch()``-es when the row is opened. The server renders
       the agent's whole conversation. Carries NO verbatim prompt /
       response / reasoning text in the initial page HTML (BUG-1) — that
       data only enters the DOM on demand.
     * ``data-probe-group`` (the agent key) + ``data-probe-id`` (the first
       seed id, for deep links).

   Verdict vocab — same single source of truth as the Findings tab evidence
   pills (QA-031): ``fail`` → EXPLOITED (red), ``pass`` → DEFENDED (green),
   ``inconclusive`` → INCONCLUSIVE (amber), empty/unset → PENDING (muted).
   The grouped row's pill is the worst-case rollup across the agent's turns
   (:func:`_rollup_verdict`).

   All ``g.*`` fields are operator-untrusted (sourced from
   ``<scan_dir>/memory.jsonl`` via :func:`_assemble_probe_groups`) — Jinja
   autoescape applies to every cell. The verbatim prompt / response /
   reasoning text never enters the initial HTML render.
#}
<table class="exec-probes-table" role="table" aria-label="Probe attempts by agent">
  <thead>
    <tr>
      <th scope="col" class="exec-probes-table__col--agent">
        {# Inner flex wrapper mirrors the body cell: "AGENT · ASI" left, "RUNS"
           pushed right so the header label sits directly above the
           right-aligned run counts. Wrapper (not the th itself) so the th stays
           a table-cell and the fixed column width is preserved. #}
        <span class="exec-probes-table__agent-head">
          <span>AGENT &middot; ASI</span>
          <span class="exec-probes-table__runs-head">RUNS</span>
        </span>
      </th>
      <th scope="col" class="exec-probes-table__col--status">STATUS</th>
      <th scope="col" class="exec-probes-table__col--verdict">VERDICT</th>
      <th scope="col" class="exec-probes-table__col--summary">SUMMARY</th>
    </tr>
  </thead>
  <tbody>
    {% for g in probe_groups %}
      {% set _verdict = g.verdict or 'unknown' %}
      {% set _rr = g.run_result %}
      {# SUMMARY — the AI-written one-liner (synthesised from all of this agent's
         turns + its rolled-up verdict) when available; falls back to the
         strongest-turn judge-reasoning gloss while a live scan is still running
         (the AI summary is generated at scan finalization). #}
      {% set _summary = g.ai_summary or (_rr.summary if _rr and _rr.has_run_result else '') %}
      <tr class="exec-probes-table__row"
          data-action="probe-row-click"
          data-probe-group="{{ g.group_key }}"
          data-probe-id="{{ g.probe_id }}"
          data-probe-href="/scan/{{ scan_id }}/probe?group={{ g.group_key | urlencode }}"
          data-source="probe"
          data-verdict="{{ _verdict }}"
          tabindex="0"
          role="button"
          aria-controls="exec-finding-slideover"
          aria-label="Open {{ g.turn_count }}-turn conversation for {{ g.agent or 'unknown agent' }}">
        <td class="exec-probes-table__cell--agent">
          <code class="exec-probes-table__asi">{{ g.asi_category or '—' }}</code>
          <span class="exec-probes-table__agent">{{ g.agent or '—' }}</span>
          {# RUNS — turn count moved next to the ASI badge (was a far-right column). #}
          <span class="exec-probes-table__runs">{{ g.turn_count }} run{{ '' if g.turn_count == 1 else 's' }}</span>
        </td>
        <td class="exec-probes-table__cell--status">
          {# Run status — completed / running / skipped. Server-rendered from the
             per-agent terminal events.jsonl signal; ``live-append.js`` updates
             it in place as ``agent_start`` / ``agent_done`` / ``agent_skipped``
             arrive over SSE. #}
          <span class="exec-probe-status exec-probe-status--{{ g.status_class or 'running' }}" data-slot="status">{{ g.status_label or 'Running' }}</span>
        </td>
        <td class="exec-probes-table__cell--verdict">
          {# Worst-case rollup pill — same single source of truth as the Findings
             tab evidence pills. Judge v2 (M5 / Stage D) gives each verdict a
             distinct pill colour via ``exec-verdict-pill--<verdict>``. #}
          <span class="exec-verdict-pill exec-verdict-pill--{{ _verdict }}">
            {%- if _verdict == 'fail' or _verdict == 'exploited' or _verdict == 'info_leak' -%}EXPLOITED
            {%- elif _verdict == 'vulnerable' -%}VULNERABLE
            {%- elif _verdict == 'needs_followup' -%}NEEDS FOLLOW-UP
            {%- elif _verdict == 'simulated_or_unverified' -%}UNVERIFIED
            {%- elif _verdict == 'pass' or _verdict == 'defended' -%}DEFENDED
            {%- elif _verdict == 'inconclusive' -%}INCONCLUSIVE
            {%- elif _verdict == 'recon' -%}RECON
            {%- else -%}PENDING
            {%- endif -%}
          </span>
        </td>
        <td class="exec-probes-table__cell--summary">
          <span class="exec-probes-table__summary">{{ _summary or '—' }}</span>
          {% if _rr and _rr.has_run_result and _rr.evaluator_attack %}
            <span class="exec-evaluator-attack" title="An attacker prompt tried to manipulate the judge on this run — not a target exploit.">⚠ evaluator-attack</span>
          {% endif %}
        </td>
      </tr>
    {% endfor %}
    {% if probe_groups | length == 0 %}<tr id="exec-probes-empty-row" class="exec-probes-table__empty-row"><td colspan="4" class="exec-empty">No probe attempts recorded yet — they appear here as the swarm runs.</td></tr>{% endif %}
  </tbody>
</table>