Submit a Plain Bug Report

1. Get bug details from the user

Ask the user for:

• Title (required) — a short summary of the bug
• Description (required) — what happened and how to trigger it.

Keep it concise but include whichever of these are available:

• Reproduction steps — a minimal code snippet or command sequence that triggers the bug. Most valuable when the bug is reproducible.
• Actual error — the traceback or unexpected output verbatim (trimmed to the relevant parts).
• Root cause / fix — if you have high-confidence insight, include it. Helps maintainers triage faster.

Not every bug will have all three — a feature that's missing or behaves incorrectly may just need a clear description.

2. Collect environment info