{% from "_macros.html" import icon %}
{#
  What the model did before answering.

  Rendered both live (streamed as a whole block, like the reasoning and the
  answer) and from the stored message afterwards, so the sources behind an
  answer stay in the transcript rather than vanishing when the stream ends.

  EVERYTHING in here is third-party text and is untrusted, exactly as much as
  model output is -- a search provider's results, an administrator's HTTP tool
  relaying whatever it was pointed at, an MCP server's reply. Jinja autoescaping
  covers it. Two things are handled separately: the URL, because `is_linkable`
  is the only thing standing between a result carrying a javascript: URL and an
  anchor pointing at it, and `event.text`, which is rendered as preformatted
  text and deliberately NOT through services/markdown.py -- markdown is the one
  path allowed to emit HTML, and this is the last content that should be given
  it.

  `kind` says how to label the event. Rows written before it existed have none,
  so web_search reads as a search and everything else falls to the generic
  branch: an old notes_search event used to claim it had searched the web.

  What a tool is *called* is not decided here. `tool_label` and `tool_icon` are
  Jinja globals over services/tool_labels.py, which is the one table the status
  line and the approval card read too. It deliberately ignores an `event.label`
  it recognises the name of: rows already on disk carry the SSH profile's name,
  so a resolver that preferred the stored value would leave every existing
  transcript saying "homeserver" where it means "Bash".
#}
{% for event in tool_events %}
{% set kind = event.kind or ('search' if event.name == 'web_search' else 'tool') %}
<details class="tool-activity {{ 'tool-activity--error' if event.status == 'error' }}">
  <summary class="tool-activity__summary">
    {{ icon(tool_icon(event), "icon--sm tool-activity__icon") }}

    <span class="tool-activity__label">
      {% if kind == 'search' %}
        {# Prose, not "Web search · mallorn". A search is the one thing here
           common enough to be worth a sentence. #}
        {% if event.status == "error" %}
          Web search failed
        {% elif event.query %}
          Searched the web for “{{ event.query }}”
        {% else %}
          Searched the web
        {% endif %}
      {% else %}
        {% set label = tool_label(event) %}
        {% if event.status == "error" %}
          {{ label }} failed
        {% else %}
          {{ label }}
        {% endif %}
        {% if event.query %}
          <span class="tool-activity__count">· {{ event.query }}</span>
        {% endif %}
      {% endif %}

      {% if event.results %}
        <span class="tool-activity__count">
          · {{ event.results | length }} result{{ '' if event.results | length == 1 else 's' }}
        </span>
      {% endif %}
    </span>
    {{ icon("chevron-down", "icon--sm reasoning__chevron") }}
  </summary>

  <div class="tool-activity__body">
    {% if event.detail and kind != 'search' %}
    <p class="tool-result__host">{{ event.detail }}</p>
    {% endif %}

    {% if event.error %}
    <p class="tool-activity__error">{{ event.error }}</p>
    {% elif not event.results and not event.text %}
    <p class="tool-activity__error">Nothing was found.</p>
    {% endif %}

    {% if event.text %}
    <pre class="tool-result__text">{{ event.text }}</pre>
    {% endif %}

    {% if event.diff %}
    {#
      What a write or an update changed, in the shape everybody already reads a
      change in.

      Every line is text off somebody's machine and is escaped exactly like the
      rest of this file. The classification reads the first character and never
      interprets the rest — a line is coloured, never parsed.

      Header lines are checked BEFORE the bare +/- ones, or `+++ b/x.py` renders
      as an addition and `--- a/x.py` as a removal at the top of every diff. The
      test is against the `a/` and `b/` prefixes rather than against three
      dashes, because a removed line whose own text begins with `--` produces
      exactly three dashes too.

      No whitespace between the spans: they are `display: block` inside a <pre>,
      so a newline between two of them is a blank line on screen.
    #}
    <pre class="diff"><code>
      {%- for line in event.diff.split("\n") -%}
        {%- if line.startswith('@@') or line.startswith('--- a/')
               or line.startswith('+++ b/') or line.startswith('diff ') -%}
          {%- set cls = 'meta' -%}
        {%- elif line.startswith('+') -%}
          {%- set cls = 'add' -%}
        {%- elif line.startswith('-') -%}
          {%- set cls = 'del' -%}
        {%- else -%}
          {%- set cls = 'ctx' -%}
        {%- endif -%}
        <span class="diff__line diff__line--{{ cls }}">{{ line }}</span>
      {%- endfor -%}
    </code></pre>
    {% endif %}

    {% for result in event.results %}
    <div class="tool-result">
      {% set scheme = (result.url or "").split(":")[0] | lower %}
      {% if scheme in ("http", "https") %}
      <a class="tool-result__title" href="{{ result.url }}"
         target="_blank" rel="noopener noreferrer nofollow">{{ result.title }}</a>
      {% else %}
      {# Not a link. A result is third-party text and its URL is not trusted to
         be safe to click. #}
      <span class="tool-result__title">{{ result.title }}</span>
      {% endif %}
      <span class="tool-result__host">{{ result.host }}</span>
      {% if result.snippet %}
      <p class="tool-result__snippet">{{ result.snippet }}</p>
      {% endif %}
    </div>
    {% endfor %}
  </div>
</details>
{% endfor %}