docs(cookbook): redact vendor-specific brand mentions per privacy lint

Author: mschaepers

docs/cookbook/_template.md

@@ -15,7 +15,7 @@ Contributor rules (see DOC-cookbook design notes):
   - Config snippets MUST be source-verified against `src/emhass/utils.py` (treat_runtimeparams)
     or `src/emhass/optimization.py`. Include `<!-- source: <file>:<line> -->` HTML comments
     above each Config / Snippet code block.
-  - Transport snippets (HA rest_command / Node-RED / EVCC / AppDaemon / Loxone) must mark
+  - Transport snippets (HA rest_command / Node-RED / EVCC / AppDaemon / vendor-native) must mark
     which stack the recipe was tested against, or mark untested variants as such.
   - Keep total length under ~200 lines including code blocks.
 -->

docs/cookbook/index.md

@@ -45,4 +45,4 @@ No recipes yet. Topics that would fit: dynamic-price (EPEX, Tibber, etc.) inject
 
 - [MPC orchestration via Node-RED](nodered_mpc_orchestration.md) — generic Node-RED → EMHASS pattern, transport-agnostic on inputs.
 
-Additional transport recipes welcome: Home Assistant `rest_command` (HA users — see [Discussion #824](https://github.com/davidusb-geek/emhass/discussions/824) for community patterns), AppDaemon, EVCC API integration (pending #29815), Loxone-direct, etc.
+Additional transport recipes welcome: Home Assistant `rest_command` (HA users — see [Discussion #824](https://github.com/davidusb-geek/emhass/discussions/824) for community patterns), AppDaemon, EVCC API integration (pending #29815), other smart-home-native integrations, etc.