issue-update

# Issue Update ## Purpose Update an existing ticket/issue with status transitions, progress comments, assignee changes, or metadata updates. Automatically uses the configured ticketing provider (Gitea, GitHub, Jira, Linear) or local file-based tracking. ## Task Given a ticket ID and update parameters: 1. **Load configuration** from `.aiwg/config.yaml` or project `CLAUDE.md` 2. **Validate ticket exists** on provider or in local files 3. **Apply updates** (status, comment, assignee, labels, priority) 4. **Return confirmation** with updated ticket details ## Parameters - **`<ticket-id>`** (required): Issue identifier (e.g., `ISSUE-001`, `#42`, `PROJECT-123`, `ENG-456`) - **`--status STATE`** (optional): Update ticket status - Valid states: `open`, `in_progress`, `closed`, `blocked`, `review` - Provider-specific mappings applied automatically - **`--comment "text"`** (optional): Add progress comment or note - **`--assignee USER`** (optional): Assign to user (or `unassigned` to clear) - **`--labels "label1,label2"`** (optional): Replace labels (comma-separated) - **`--add-labels "label1,label2"`** (optional): Add labels without replacing existing - **`--remove-labels "label1,label2"`** (optional): Remove specific labels - **`--priority LEVEL`** (optional): Update priority (low|medium|high|critical) - **`--milestone NAME`** (optional): Associate with milestone (provider-dependent) - **`--provider NAME`** (optional): Override configured provider ## Inputs **Configuratio...