{% load common_extras %}{% comment %} A comment trigger. Everything here is platform-agnostic: L4-A shipped the config, the matcher and the once-per-commenter guard, and each adapter registers what its own API can do (apps/flows/triggers/comments.py). Nothing below names a platform. Two things are driven by that registry rather than by markup: * the post picker appears once per platform that ships one, and loads over htmx into the panel below the textarea — which stays editable, because an older post that is not on the first page is still configurable by pasting its id; * "Like the comment" appears only while some platform this trigger can fire on has an API for it. Instagram has none — Meta's IG Comment reference exposes like_count as read-only and only hide and replies as write operations — so on an Instagram-only deployment the option is absent rather than silently ignored. {% endcomment %}
{% if post_pickers %}
{% for picker in post_pickers %} {% endfor %}
{% endif %} {% if like_supported %} {% elif config.like_comment %} {% comment %} Hidden, not dropped. An unchecked checkbox posts nothing, so simply omitting the control would silently clear a setting the author made — on an unrelated edit, with nothing to say so. The value is their stated intent, and whether a platform can honour it is a fact that changes when an adapter ships. {% endcomment %} {% endif %}

The public reply goes out first; the flow's first message follows as a private reply, once per comment and within seven days of it.