docs v1.44.1: add the Telegram community chat (@ha_houseplan)

- badges + header line in README.md / README.ru.md
- 'Getting help & sharing your plan' section in both READMEs, asking for
  the version number when reporting (console banner / integration page)
- .github/ISSUE_TEMPLATE/config.yml contact links (chat + discussions)
- CONTRIBUTING 'Where to ask'; STATUS (community row) and SCOPE (field
  feedback source)

docs/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## v1.44.1 — 2026-07-27
+- Added the community chat everywhere users look: **https://t.me/ha_houseplan**
+  (badge and header line in both READMEs, a "Getting help" section, the issue
+  template contact links, CONTRIBUTING, STATUS and SCOPE).
+
 ## v1.44.0 — 2026-07-27 (user feedback: control first)
 
 - **The device card is now a control surface.** It opens with the device's

docs/SCOPE.md

@@ -91,6 +91,9 @@ Editors are admin-only tools and must never leak interactions into View
 unlocked/new device) · safe quick actions · per-room climate · Zigbee mesh
 health · zero-to-plan GUI onboarding · keeping the plan true over years.
 
+**Where users are:** Telegram chat https://t.me/ha_houseplan (support, feature
+signals, screenshots) — treat it as the primary source of field feedback.
+
 **Pains it removes:** hand-crafted SVG + YAML floorplans · entity-list
 dashboards that hide *where* things happen · silent device sprawl · accidental
 toggles of security devices · per-device dashboards that non-technical family

docs/STATUS.md

@@ -21,6 +21,7 @@
 | Home instance | ha.jbstudio.pro (SSH port 323, key `ha_jb`), deployed **v1.41.0** via direct copy (HACS custom repo also installed) |
 | Localization | UI en/ru (src/i18n/*.json), everything user-visible localized incl. kiosk popover |
 | Tests | 111 frontend (node:test) + 12 pure backend + 12 HA-harness (CI, py3.13); ~30 demo smoke suites (headless chromium) |
+| Community | **Telegram chat: https://t.me/ha_houseplan** (created 2026-07-27) — the primary user-facing support channel; GitHub issues stay for bugs/features. Link it from any new release notes and posts |
 | Product scope | docs/SCOPE.md (2026-07-22) is the feature guard rail — check before accepting any feature |
 
 ## Current feature surface (since the 2026-07-17 snapshot)