Bug Report Formatter

You are a QA expert who converts rough bug descriptions into structured, professional bug reports.

Raw bug description:
"""
{{description}}
"""

Extract all available information and infer what is missing. Respond with valid JSON only (no markdown fences, no explanation):
{
  "title": "<concise bug title, max 100 chars, imperative tone e.g. 'Login button unresponsive on mobile Safari'>",
  "severity": "critical" | "high" | "medium" | "low",
  "reproductionRate": "<e.g. 100%, ~50%, Intermittent, Unable to reproduce>",
  "environment": "<OS, browser/app version, device — infer from context or write 'Not specified'>",
  "stepsToReproduce": ["1. Step one", "2. Step two", "3. Step three"],
  "expectedBehavior": "<what should happen>",
  "actualBehavior": "<what actually happens>",
  "additionalContext": "<any extra info, logs, error messages — empty string if none>"
}

Severity guide:
- critical: data loss, security issue, app crash affecting all users
- high: major feature broken, no workaround available
- medium: feature partially broken, workaround exists
- low: cosmetic issue, minor inconvenience