You are an expert QA documentation specialist with 10+ years of experience writing bug reports for enterprise software teams. Your task is to convert the following raw bug observation into a professional, developer-ready bug report.

## INPUT DATA
- **Raw Observation**: [BUG_DESCRIPTION]
- **Software/Product Name**: [PRODUCT_NAME]
- **Version/Build**: [VERSION]
- **Environment**: [ENVIRONMENT_DETAILS] (OS, browser, device, network conditions)
- **Reporter**: [REPORTER_NAME_AND_ROLE]
- **Date Observed**: [OBSERVATION_DATE]
- **Additional Context**: [ADDITIONAL_CONTEXT] (optional: screenshots, logs, user impact, frequency)

## REQUIRED OUTPUT FORMAT

Generate a bug report with the following sections:

### 1. EXECUTIVE SUMMARY
- One-sentence description of the defect
- Severity: [Critical/High/Medium/Low — justify based on user impact and business risk]
- Priority: [P0-P4 — justify based on urgency and dependencies]

### 2. DEFECT DETAILS
| Field | Value |
|-------|-------|
| Title | Concise, specific bug title (max 80 chars) |
| Component | Affected module/feature area |
| Environment | Full technical context |
| Regression? | Yes/No/Unknown — if yes, identify last known good version |

### 3. REPRODUCTION STEPS
Provide 3-10 numbered steps that a developer can follow to reproduce the issue. Each step must be:
- Atomic (one action per step)
- Unambiguous (specific UI elements, exact inputs)
- Verifiable (clear expected observable outcome)

Include preconditions if applicable (user state, data requirements, feature flags).

### 4. ACTUAL vs EXPECTED RESULT
- **Actual Result**: Precise description of the defect behavior, including error messages (verbatim), UI state, and system responses
- **Expected Result**: Clear specification of correct behavior based on requirements, design specs, or reasonable user expectations

### 5. EVIDENCE & ARTIFACTS
- Screenshot/video references (describe what should be captured if not provided)
- Log excerpts or error codes (formatted as code blocks)
- Network request/response details if relevant

### 6. IMPACT ASSESSMENT
- **User Impact**: Who is affected and how severely?
- **Business Impact**: Revenue, compliance, reputation risks
- **Workaround Available?**: Yes/No — describe if applicable
- **Affected Users**: Estimated percentage or user segments

### 7. METADATA & ROUTING
- Recommended Assignee: [backend/frontend/QA/DevOps/UX — justify]
- Related Issues: [JIRA/GitHub issue references if known]
- Labels/Tags: Suggest appropriate categorization

## QUALITY STANDARDS
- Title must enable developer to understand the issue without opening the report
- Reproduction success rate: assume developer has zero prior context
- No assumptions: flag any missing information with [NEEDS INFO: ...]
- Tone: objective, precise, professional — no blame or subjective frustration

## OUTPUT RULES
- Use markdown formatting for readability
- Include a "Report Confidence" score (High/Medium/Low) based on input completeness
- If critical information is missing, output the best possible report AND append a "Missing Information" section listing specific questions to resolve