Bug Diagnosis Prompt

Turn the supplied inputs into **bug diagnosis prompt**. Optimize for the person searching “bug diagnosis prompt”: they need a clear result, the reasoning that affects it, and an obvious next step.

## Situation to solve — Bug Diagnosis Prompt
- [ACTUAL_BEHAVIOR] — for Bug Diagnosis Prompt, supply the relevant actual behavior. If unavailable, label [ACTUAL_BEHAVIOR] `unknown`; never infer it.
- [CONSTRAINTS] — for Bug Diagnosis Prompt, supply the relevant constraints. If unavailable, label [CONSTRAINTS] `unknown`; never infer it.
- [LANGUAGE] — for Bug Diagnosis Prompt, supply the relevant language. If unavailable, label [LANGUAGE] `unknown`; never infer it.
- [EXPECTED_BEHAVIOR] — for Bug Diagnosis Prompt, supply the relevant expected behavior. If unavailable, label [EXPECTED_BEHAVIOR] `unknown`; never infer it.
- [REPRODUCTION_STEPS] — for Bug Diagnosis Prompt, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it.
- [CODE] — for Bug Diagnosis Prompt, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it.
- [EVALUATION_CRITERIA] — for Bug Diagnosis Prompt, supply the relevant evaluation criteria. If unavailable, label [EVALUATION_CRITERIA] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for Bug Diagnosis Prompt, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## How to work — Bug Diagnosis Prompt
1. Establish pass/fail criteria before reviewing the material.
2. Score each finding by evidence, impact, confidence, and effort; quote or point to the relevant input.
3. Trace observable behavior through the relevant code path before editing anything.
4. Provide the smallest defensible patch, regression tests, and exact verification steps.
5. Include tests that would fail before the correction.
6. Reproduce or reason from the observed failure before proposing a fix.
7. Identify the smallest causal code path.
8. Separate confirmed behavior from hypotheses.
9. Boundary for Bug Diagnosis Prompt: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Make the answer usable — Bug Diagnosis Prompt
- **Technical finding for Bug Diagnosis Prompt** — bug diagnosis prompt evidence → Bug Diagnosis Prompt; omit preamble.
- **Evidence or reproduction for Bug Diagnosis Prompt** — material inputs for Bug Diagnosis Prompt, each connected to bug diagnosis prompt.
- **Minimal change for Bug Diagnosis Prompt** — ready-to-use Bug Diagnosis Prompt, formatted for bug diagnosis prompt.
- **Test coverage for Bug Diagnosis Prompt** — Bug Diagnosis Prompt weak points, unknowns, and bug diagnosis prompt limits.
- **Verification command for Bug Diagnosis Prompt** — bug diagnosis prompt → verify Bug Diagnosis Prompt before use.

## Integrity check — Bug Diagnosis Prompt
Finish with a compact integrity check for Bug Diagnosis Prompt: factual support, task fit, internal consistency, usability, and required human review.