iw-new-incidentlisted

# New Incident Creator Create a complete incident fix package for the current project. **Issue description**: $ARGUMENTS --- ## Step 1: Reserve Incident ID Reserve the next available Incident ID **immediately** to prevent concurrent agents from claiming the same number. ```bash iw next-id --type incident ``` This atomically allocates the next ID (e.g., `I-00005`) using a database row-lock — no file reading needed, no race conditions possible. Store the returned ID **exactly as printed** — you will use it verbatim throughout. **CRITICAL**: The `iw next-id` call MUST happen before ANY other work. The ID is reserved the moment the call returns. **CRITICAL**: Use the ID **exactly as returned** (format: `I-NNNNN`). Do NOT look for tracking files, do NOT use a manually chosen number, do NOT override or "adjust" the returned value for any reason. The database is the sole source of truth for IDs. ## Step 2: Investigate the Issue ### 2a: Gather Bug Details (MANDATORY INTERACTION) **NEVER skip this step.** Even if `$ARGUMENTS` seems detailed, ALWAYS discuss with the user to ensure alignment. Use `$ARGUMENTS` as a starting point for the conversation, not as final input. Present what you understood from `$ARGUMENTS`, then ask the user to confirm or correct: 1. **What is broken?** (expected vs actual behavior) 2. **Steps to reproduce** (numbered sequence) 3. **Severity**: Critical / High / Medium / Low 4. **Where was it discovered?** (user report, CI failure, code review, te