Bug Report

Turn a defect into a report a maintainer can act on without a follow-up conversation: evidence they can re-run, a root cause named with file:line when established, verification status, and an honest account of what you did not check. Unknown causes and unverified fixes are useful when labelled honestly.

Success artifact: a single .md file whose every factual claim traces to output you actually captured. Filing it anywhere follows the user's intent and applicable routing guidance (step 6); the local file alone is a complete outcome.

Inputs

$ARGUMENTS — the defect, the repo, or both. If neither is clear, ask what's broken and which repo owns it before proceeding.