Update BearClaw and Telegram bot YAML configurations to clarify decision logic and transport roles. Added notes to emphasize the separation of responsibilities between BearClaw and codex_appliance, and refined chunking logic in the Telegram bot script for improved message handling.

config/packages/bearclaw.yaml

@@ -7,6 +7,8 @@
 #  Routes Telegram -> codex_appliance and codex_appliance -> Telegram/HA.
 # -------------------------------------------------------------------
 # Notes: Keep BearClaw transport + bridge logic centralized in this package.
+# Notes: Most BearClaw decision logic runs in docker_17/codex_appliance (server.js).
+# Notes: GitHub capture behavior (issue creation/labels/research flow) belongs in codex_appliance, not HA YAML.
 ######################################################################
 
 rest_command:

config/packages/telegram_bot.yaml

@@ -8,6 +8,7 @@
 # -------------------------------------------------------------------
 # Notes: Do not add `telegram_bot:` YAML here; integration is UI-only.
 # Notes: Joanna transport sends as plain_text to avoid Telegram parse-entity failures.
+# Notes: Keep Skills logic in docker_17/codex_appliance; this package is delivery/transport only.
 ######################################################################
 
 script:
@@ -39,7 +40,7 @@ script:
           count: "{{ total_chunks | int(1) }}"
           sequence:
             - variables:
-                start: "{{ repeat.index0 * (chunk_size | int(3400)) }}"
+                start: "{{ ((repeat.index | int(1)) - 1) * (chunk_size | int(3400)) }}"
                 stop: "{{ start + (chunk_size | int(3400)) }}"
                 chunk_body: "{{ safe_message[start:stop] }}"
                 chunk_message: >-