{# Spec 148 — Recommended physical layout card(s).

   Read-only recommendation: no diff, no Apply button, no copyable
   ALTER. Renders a partition + cluster suggestion derived from how
   the table is actually queried in the cached scan window.

   ``layout_recommendations`` is a list of zero or more
   ``LayoutRecommendation`` objects — one per qualifying target
   table. For ``partition_pruning`` opportunities the targets are
   the upstream tables the bad query was reading from, NOT the
   downstream that the opportunity is anchored to. The
   ``{% for %}`` loop renders one card per target; an empty list
   produces zero markup. #}
{% for layout_recommendation in (layout_recommendations or []) %}
<div class="ui-surface p-6 mt-6">
  <div class="flex flex-wrap items-center gap-3">
    <h2 class="ui-section-title">Recommended physical layout</h2>
    {% if layout_recommendation.table %}
      <code class="font-mono text-xs text-slate-500 dark:text-slate-400">{{ layout_recommendation.table }}</code>
    {% endif %}
  </div>
  <p class="mt-2 text-sm text-slate-500 dark:text-slate-400">
    Based on how this table's data is queried across the scan window. Audit
    doesn't modify your SQL — apply the recommendation manually via
    <code class="text-xs">ALTER TABLE … SET OPTIONS(...)</code> or in your
    dbt model config.
  </p>

  {% if layout_recommendation.partition %}
  <div class="mt-5 border-l-2 border-brand-500/40 pl-4">
    <h3 class="text-sm font-semibold text-slate-700 dark:text-slate-200">
      Partition by
      <code class="font-mono text-brand-600 dark:text-brand-300">{{ layout_recommendation.partition.column }}</code>
      <span class="ui-pill ui-pill-neutral text-[11px]">{{ layout_recommendation.partition.column_type }}</span>
    </h3>
    <p class="mt-2 text-sm text-slate-700 dark:text-slate-300 leading-relaxed">
      {{ "%.0f" | format(layout_recommendation.partition.filter_frequency * 100) }}%
      of consumer queries ({{ layout_recommendation.partition.consumer_job_count }} jobs in window)
      filter on this column.
      Table is currently
      {% if layout_recommendation.evidence.is_partitioned %}partitioned by another column{% else %}unpartitioned{% endif %}{% if layout_recommendation.evidence.total_bytes %},
      {{ layout_recommendation.evidence.total_bytes | format_bytes }} total{% endif %}.
    </p>
  </div>
  {% endif %}

  {% if layout_recommendation.cluster %}
  <div class="mt-5 border-l-2 border-brand-500/40 pl-4">
    <h3 class="text-sm font-semibold text-slate-700 dark:text-slate-200">
      Cluster on
      <code class="font-mono text-brand-600 dark:text-brand-300">({% for c in layout_recommendation.cluster %}{{ c.column }}{% if not loop.last %}, {% endif %}{% endfor %})</code>
    </h3>
    <p class="mt-2 text-sm text-slate-700 dark:text-slate-300 leading-relaxed">
      Top column appears in
      {{ "%.0f" | format(layout_recommendation.cluster[0].filter_or_join_frequency * 100) }}%
      of WHERE / JOIN clauses across
      {{ layout_recommendation.evidence.total_consumer_jobs }} consumer queries.
      {% if layout_recommendation.cluster | length > 1 %}
        Cluster ordering matters in BigQuery — listed columns are ordered
        by usage frequency descending.
      {% endif %}
    </p>
  </div>
  {% endif %}

  <p class="mt-5 text-xs text-slate-500 dark:text-slate-400 italic">
    No SQL diff is generated for partition / cluster — these are physical-layout
    properties, not query rewrites. Audit surfaces the recommendation; you
    apply it.
  </p>
</div>
{% endfor %}