feat(rules): доступ к Redmine (red.eltex.loc) через API-ключ

Правило №6: читать задачи Redmine по персональному API-ключу из
~/.config/ai-setup/redmine_key, вытаскивать ТЗ/статус/комментарии
через /issues/<N>.json?include=journals. Ключ держать только в этом
файле, не вписывать в git.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

home-configs/GLOBAL_RULES.md

@@ -90,3 +90,11 @@ The rules below are mandatory for every interaction and task. They are intention
    Keep skills focused: prefer several small skills over one broad skill. A useful skill should have a precise description for when to use it, short instructions for how to act, and reusable tools, templates, references, or examples when they make the result more stable.
 
    If skill files are outside the current git repository, clearly state the exact paths changed and how the user can inspect them, because those changes are not visible in the project `git diff`.
+
+6. **Redmine (red.eltex.loc) access:**
+   Redmine issues require authentication. To read a task's spec and comments, use the personal API key stored in `~/.config/ai-setup/redmine_key` (chmod 600). Eltex branches usually start with the issue number (e.g. `485448_keyboard_opening_fix` → issue `485448` → https://red.eltex.loc/issues/485448). Fetch the issue with its comments (journals) via:
+   ```bash
+   curl -s -H "X-Redmine-API-Key: $(cat ~/.config/ai-setup/redmine_key)" \
+     "https://red.eltex.loc/issues/<N>.json?include=journals"
+   ```
+   Read `issue.description` for the spec, `issue.journals[].notes` for comments (recent non-empty ones matter most), `issue.status.name` for status. Keep the key only in that file — never write it into files tracked by git.