redmine skill 1.2: Bearbeiter nicht zuweisen

Notiz und Status setzen ist in Ordnung, assigned_to_id nicht anfassen —
das entscheidet der User selbst.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

redmine-issue-workflow/SKILL.md

@@ -3,7 +3,7 @@ name: redmine-issue-workflow
 description: "Read and update issues on a self-hosted Redmine via its REST API from the CLI — list/read tickets, add notes, change status, edit an existing journal note in place, and download attachments. Use when a project tracks its work/bugs in Redmine and you need to look up 'the next fixes', check a ticket's details, mark work done, or maintain a collection ('Sammelticket') ticket. Covers: API-key auth via header (never inline the secret), the issues/journals/attachments endpoints, Textile (NOT Markdown) formatting, localized statuses, and the posting-style rules (keep customer-visible notes minimal — strike through or 'erledigt', don't write the bug's cause; don't post unless asked)."
 metadata:
   author: Wappler
-  version: "1.1"
+  version: "1.2"
 ---
 
 # Redmine issue workflow (REST API, CLI)
@@ -62,6 +62,9 @@ Redmine renders **Textile** by default. Consequences:
   no before/after measurements — the customer did not ask how, only whether.
 - **No icons, emoji or decorative symbols in ticket text** (no ✅/✔/→/⚠, no bullets made of glyphs).
   Plain sentences, plus Textile markup where it carries meaning (strike-through, bold). Team rule.
+- **Never set or change `assigned_to_id`.** Post the note and the status, leave the assignee alone —
+  reassigning is the user's call and a wrong one pulls a colleague into a ticket that isn't theirs.
+  Note that `status_id` and `done_ratio` are fine to set; only ownership is off limits.
 - Before posting a status change, prefer to draft the (short, German if the project is German) note and
   confirm the target status with the user.