bug-triagelisted

# Bug Triage and Fix Analysis Use this skill when turning a bug report, exception, stack trace, failing test, or support signal into a bounded investigation and an owned next action. It helps distinguish a reproducible defect from a usage question, environment issue, duplicate, regression, or insufficient evidence. It does not claim to have accessed an issue tracker or repository unless that source was actually provided or authorized. ## Intake and evidence quality Capture the report ID or safe local reference, reporter context, first and most recent occurrence, time zone, affected version, environment, user-visible symptom, frequency, severity, workaround, and privacy classification. Preserve the original wording separately from normalized summaries. Mark each field as observed, reported, inferred, or unknown. Request the smallest useful reproduction: exact input shape without secrets, expected and actual behavior, deterministic steps, a known-good comparison, relevant configuration, and the narrowest logs or trace. Redact tokens, credentials, personal data, private URLs, and confidential payloads before sharing or storing evidence. Do not ask a reporter to expose production data just to improve a ticket. ## Analyze errors and stack traces 1. Confirm the exception or failure is from the claimed component and version. 2. Read the stack from the failure boundary outward, distinguishing the first application frame from framework or wrapper frames. 3. Identify inputs, s