Comment auto-reply reasons like hourly_cap and loop_guard are recorded, but nothing resolves whether auto-reply is on.
What
The pipeline that reacts to comments on published artifacts now records a status for each comment thread rather than just succeeding or vanishing: declined with a reason such as blocked, auto_reply_off, plan_mode, hourly_cap, loop_guard or denied_by_rule, or failed with compose_failed or post_failed. Threads seen for the first time can be deferred instead of dropped. Nothing in the build resolves whether the surrounding auto-reply feature is on for a given account.
Evidence
"deferred_first_sight"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.