{% extends "base.html" %}
{% block title %}Workflows{% endblock %}
{% block content %}
<section class="page-head">
  <h1>Workflows</h1>
  <p class="page-sub">
    {{ workflows|length }} registered.
    {% if allow_run %}
      Click <strong>Run</strong> to execute one. Output streams below.
    {% else %}
      Read-only mode — restart without <code>--read-only</code> to run from the dashboard.
    {% endif %}
  </p>
</section>

{# Multi-actor bulletin strip — shows in-flight runs from OTHER actors
   (other Claude Code sessions, CLI invocations, scheduled tasks). The
   container is empty on first paint; bulletin.js polls
   /api/bulletin/active every 5s and renders chips. The whole section
   stays hidden via the ``hidden`` attribute when zero entries are
   active, so it doesn't add visual noise in single-actor workflows.
   See docs/specs/multi-actor-bulletin/. #}
<section id="bulletin-strip" class="bulletin-strip" hidden>
  <h2 class="bulletin-strip-title">
    Now running across actors
    <span class="bulletin-strip-count" id="bulletin-strip-count">0</span>
  </h2>
  <div class="bulletin-strip-chips" id="bulletin-strip-chips"></div>
</section>

{% if workflows %}
  <table class="data-table runner-table">
    <thead>
      <tr>
        <th>Name</th>
        <th>Tier map</th>
        <th>Description</th>
        <th>Scope</th>
        {% if allow_run %}<th class="num">Action</th>{% endif %}
      </tr>
    </thead>
    <tbody>
      {% for w in workflows %}
        {# data-scope-default carries the first-paint default scope
           for this workflow, auto-derived server-side from
           features.yaml. runner.js reads it on DOMContentLoaded if
           localStorage has no saved scope. Empty string means
           "project-wide is the default" — explicitly chosen for
           workflows like release-prep / health-check that don't map
           to a single feature. #}
        <tr data-workflow="{{ w.name }}"
            data-scope-default="{{ default_scopes[w.name] if supports_path[w.name] else '' }}">
          <td><code>{{ w.name }}</code></td>
          {# Chip text: humanized stage name + friendly tier descriptor.
             - Stage names like ``agent-review`` strip the ``agent-`` prefix
               and title-case for readability (``Review``).
             - Tier names like ``capable`` map through TIER_LABEL to
               ``Standard``; the underlying Claude model class is
               surfaced in the tooltip via TIER_TOOLTIP so the chip stays
               compact while the hover affordance carries the detail. #}
          <td>
            {% for stage, tier in w.tier_map.items() %}
              {% set stage_label = stage.replace('agent-', '').replace('-', ' ').replace('_', ' ').title() %}
              <span class="chip chip-{{ tier|lower }}"
                    data-tooltip="{{ tier_tooltip.get(tier|lower, tier) }}"
                    aria-label="{{ stage_label }} stage, {{ tier_label.get(tier|lower, tier) }} tier">{{ stage_label }} {{ tier_label.get(tier|lower, tier) }}</span>
            {% endfor %}
            {% if not w.tier_map %}
              <span class="muted"
                    data-tooltip="Meta-orchestration workflow — composes other workflows rather than declaring its own stages."
                    aria-label="Meta-orchestration workflow">—</span>
            {% endif %}
          </td>
          <td>
            {{ w.description }}
            <div class="run-status"><span data-status></span></div>
            {% if w.name == "discovery-sweep" %}
              {# Phase 3 chips. Server-rendered for first paint; runner.js
                 refreshes them on scope-picker change via
                 /api/workflows/discovery-sweep/chips. Anchor hrefs link to
                 the scope-keyed detail page filtered by bucket. #}
              <div class="sweep-chip-row" data-sweep-chips
                   data-scope-hash="{{ sweep_chips.scope_hash }}"
                   data-has-result="{{ '1' if sweep_chips.has_result else '0' }}">
                <a class="chip chip-danger" data-chip="queue"
                   href="/workflows/discovery-sweep/results/{{ sweep_chips.scope_hash }}?bucket=queue"
                   data-tooltip="Findings ready for review">
                  queue: <span data-chip-count>{{ sweep_chips.queue }}</span>
                </a>
                <a class="chip chip-warn" data-chip="questions"
                   href="/workflows/discovery-sweep/results/{{ sweep_chips.scope_hash }}?bucket=questions"
                   data-tooltip="Findings the engine couldn't auto-route">
                  questions: <span data-chip-count>{{ sweep_chips.questions }}</span>
                </a>
                <a class="chip chip-muted" data-chip="rejected"
                   href="/workflows/discovery-sweep/results/{{ sweep_chips.scope_hash }}?bucket=rejected"
                   data-tooltip="Findings filtered out by deterministic rules">
                  rejected: <span data-chip-count>{{ sweep_chips.rejected }}</span>
                </a>
                <span class="sweep-chip-status muted" data-sweep-chip-status
                      {% if not sweep_chips.has_result %}data-empty="1"{% endif %}>
                  {% if sweep_chips.has_result %}latest result{% else %}no sweep recorded for this scope yet{% endif %}
                </span>
              </div>
            {% endif %}
            <div class="recent-runs" data-recent-runs="{{ w.name }}" hidden></div>
            <div class="log-pane" data-log-pane hidden>
              <pre data-log class="log-output"></pre>
            </div>
          </td>
          {# Scope cell renders in both run and read-only modes (AC-6).
             In read-only mode the picker still pre-selects the saved
             scope so the choice persists for when the user enables
             runs; only the Action column hides. #}
          <td class="scope-cell">
            {% if supports_path[w.name] %}
              <select class="scope-picker" data-scope-picker aria-label="Scope for {{ w.name }}">
                {# "All code" is the top option and the catch-all default
                   for workflows without a specific feature mapping (the
                   per-row ``data-scope-default=""`` still signals "no path
                   argument" to the runner — the visible label just
                   replaces the misleading "Project-wide" with what the
                   workflow actually scans). #}
                <option value="" title="All source code under {{ all_code_path }} — broad scan, no path argument passed">All code ({{ all_code_path }})</option>
                {% for f in features %}
                  {% if f.path %}
                    <option value="{{ f.path }}" title="{{ f.description }}">{{ f.name }}</option>
                  {% endif %}
                {% endfor %}
                <option value="__custom__">Custom path…</option>
              </select>
              <input type="text" class="scope-custom" data-scope-custom hidden
                     placeholder="e.g. src/attune/security/"
                     aria-label="Custom scope path for {{ w.name }}">
            {% else %}
              <span class="scope-na"
                    data-tooltip="This workflow doesn't accept a path argument"
                    aria-label="This workflow doesn't accept a path argument">n/a</span>
            {% endif %}
          </td>
          {% if allow_run %}
            <td class="num">
              <button class="btn btn-run" type="button" data-run-button data-workflow="{{ w.name }}" aria-label="Run {{ w.name }}">Run</button>
            </td>
          {% endif %}
        </tr>
      {% endfor %}
    </tbody>
  </table>
{% else %}
  <p class="empty">No workflows are visible. Make sure <code>attune-ai</code> is installed in the same venv as <code>attune-ops</code>.</p>
{% endif %}
{% endblock %}

{% block scripts %}
{# Server-injected workspace root, read by runner.js to validate that
   a saved scope from localStorage is still under this workspace
   (catches stale scopes from a different worktree). The old
   firstFeaturePath / allCodePath fields used to live here too but
   moved to per-row ``data-scope-default`` attributes (rendered above)
   so each workflow can default to its own most-relevant scope. #}
<script id="scope-picker-config" type="application/json">
{"workspaceRoot": {{ workspace_root | tojson }}}
</script>
{# runner.js is loaded unconditionally so the recent-runs strip
   renders in both run and read-only modes. The script's
   DOMContentLoaded handler queries for run-button / scope-picker
   elements that only exist when allow_run is True, so the read-only
   page sees a no-op for those features. #}
<script src="{{ url_for('static', path='js/runner.js') }}?v={{ attune_version }}"></script>
{# bulletin.js polls /api/bulletin/active every 5s to populate the
   "Now running across actors" strip rendered above. Loaded
   unconditionally so the strip appears in both run and read-only
   modes — read-only dashboards can still surface OTHER actors' work. #}
<script src="{{ url_for('static', path='js/bulletin.js') }}?v={{ attune_version }}"></script>
{% endblock %}