Fixed
{{ rule_name }}available in top-level templates and throttle key (issue #31).rule_nameis now injected into the render context oftemplates.<name>.title,body, andemail_body_html, and also into thethrottle.keytemplate, not just the notifier-levelsubject_template/body_template. Configs that referenced{{ rule_name }}in a top-level template previously rendered an empty string; they now render the rule name. If an event field happens to be literally namedrule_name, the synthetic rule name wins, matching the collision policy of the existing notifier-level contexts.- Dotted event fields resolve in
throttle.key. The unflatten step introduced in v1.2.0 for template rendering (issue #25) now also applies to the throttle key template, sothrottle.key: "{{ nginx.http.status_code }}-{{ hostname }}"works consistently withtitle/body.