Triage issue reports
- Normalize the report into product area, environment, steps, expected behavior, observed behavior, frequency, and supplied evidence.
- Search for duplicates and known limitations when issue/search capabilities exist.
- Inspect the relevant code/feature map enough to judge plausibility without making edits.
- Classify as confirmed-enough-to-reproduce, needs-reporter-information, duplicate, expected behavior, or currently untriageable.
- Reply in the source thread/ticket when available with concise rationale and the next action. Do not invent a reproduction.