feat(tickets): open, comment and resolve tickets from the UI and MCP; known issues on alerts and anomalies (#6351, #6352)

A ticket records a known problem: title, area, hosts, subject, description,
links to alert rules and anomalies, and a log of comments, edits, resolving
and reopening. Opening, resolving (with the resolution as the note) and
reopening go on the timeline; every step is audited, and the audit rows stay
off the timeline.

An alert or anomaly an open ticket covers (by link, by subject, or a
host-wide ticket on the host itself) shows a Known issue badge, and offers
"Open a ticket" prefilled from its rule or anomaly when none does. Hosts,
monitors and containers get a Known issues card.

MCP: list_tickets, get_ticket (viewer); open_ticket, update_ticket,
comment_ticket, resolve_ticket, reopen_ticket (operator). list_alerts and
list_anomalies carry known_issue; get_overview, get_host, get_monitor and
get_container carry open_tickets. Also update_change and delete_change for
changes recorded by hand (author or admin).

Tickets are left out of backups, like the timeline (2026-10-15 ruling).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

steward/templates/alerts/_active.html

@@ -3,7 +3,8 @@
    there are and where their notifications go; then the alerts themselves,
    firing first, then no data, then acknowledged, then pending
    (alert_svc.active_rows). An acknowledged alert says how long it has been
-   breaching, and apart from that who acknowledged it and when. #}
+   breaching, and apart from that who acknowledged it and when. One an open
+   ticket covers is a known issue, linked to it; the rest offer a ticket. #}
 {% from "_macros.html" import status_badge %}
 {% set can_edit = session.user_role in ('operator', 'admin') %}
 {% set words = {"firing": "firing", "no_data": "silent", "acknowledged": "acknowledged", "pending": "pending"} %}
@@ -46,6 +47,10 @@
                     {{- row.says.lead -}}
                     {%- if row.url %}<a href="{{ row.url }}">{{ row.says.resource }}</a>{% else %}<strong>{{ row.says.resource }}</strong>{% endif -%}
                     {{- row.says.tail -}}
+                    {%- if row.tickets %}
+                    <div class="field-hint" style="margin-top:0.15rem;">{{ status_badge("known_issue") }}
+                      {% for t in row.tickets %}<a href="/tickets/{{ t.id }}">#{{ t.id }} {{ t.title }}</a>{{ ", " if not loop.last }}{% endfor %}</div>
+                    {%- endif %}
                     {%- if row.label == 'acknowledged' and row.state.acknowledged_at %}
                     <div class="field-hint" style="margin-top:0.15rem;">Acknowledged{% if row.acked_by %} by {{ row.acked_by }}{% endif %} {{ row.state.acknowledged_at|ago }}</div>
                     {%- endif %}
@@ -57,6 +62,10 @@
                         <button type="submit" class="btn btn-sm btn-warn">Acknowledge</button>
                     </form>
                     {% endif %}
+                    {% if can_edit and not row.tickets %}
+                    <a class="btn btn-sm btn-ghost" href="/tickets/new?rule={{ row.rule.id|urlencode }}&amp;back=/alerts/"
+                       title="A known problem that will take a while: keep its notes and its fix in one place">Open a ticket</a>
+                    {% endif %}
                 </td>
             </tr>
             {% endfor %}