docs(security): state response-time SLA in the security issue template

.github/ISSUE_TEMPLATE/security.md

@@ -10,6 +10,16 @@ assignees: ''
 
 **For non-sensitive security-related issues only:**
 
+### What to expect
+
+Per our [Security Policy](../../SECURITY.md#response-timeline), the same response timeline applies to reports filed here:
+
+- **Initial Response**: Within 48 hours of receiving your report
+- **Status Update**: Within 7 days with our assessment and planned timeline
+- **Resolution**: We aim to resolve critical vulnerabilities within 30 days
+
+If you have not heard from us within 48 hours, please ping the issue or reach out through our [community Telegram](https://t.me/+DOylgFv1jyJlNzM0).
+
 ## Description
 A clear and concise description of the security concern.
 

SECURITY.md

@@ -46,6 +46,10 @@ We are committed to responding to security reports promptly:
 - **Status Update**: Within 7 days with our assessment and planned timeline
 - **Resolution**: We aim to resolve critical vulnerabilities within 30 days
 
+These targets apply to every reporting channel — private GitHub Security Advisories and non-sensitive public reports filed with the [security issue template](.github/ISSUE_TEMPLATE/security.md), which restates the same timeline. If you update one, update the other so they do not drift.
+
+If you have not heard from us within 48 hours, please reach out through our [community Telegram](https://t.me/+DOylgFv1jyJlNzM0).
+
 ### Disclosure Policy
 
 - We follow responsible disclosure practices
@@ -106,7 +110,7 @@ Security updates and advisories will be published:
 
 For security-related questions or concerns that are not vulnerabilities, you can:
 
-- Open a public issue with the `security` label
+- Open a public issue with the `security` label using the [security issue template](.github/ISSUE_TEMPLATE/security.md)
 - Reach out to the maintainers through GitHub
 - Join our community discussions