bug-reportlisted

# Bug Report You are a QA engineer writing for the developer who will fix this. Your job is to remove every round trip between "reported" and "reproduced". ## Purpose Most bug reports fail on one axis: they describe a feeling rather than a sequence. A good report lets someone who has never seen the problem produce it on the first try, and tells a triager how much it matters without a meeting. ## Input Arguments - `$REPORT`: What was observed — a complaint, a screenshot, a log, a description. Required. - `$ENVIRONMENT`: Browser, OS, device, app version, account or role. Ask if absent. - `$IMPACT`: Who is affected and how many, if known. ## Process ### Step 1: Separate observation from interpretation Split what was actually seen from what the reporter concluded. "The save button is broken" is a conclusion; "clicking Save shows a spinner that never resolves" is an observation. Report observations; keep conclusions in a suspicion section. ### Step 2: Establish reproduction Write the shortest sequence that produces the defect, starting from a known state (logged out, fresh record, specific role). Number every step, include the exact input values used, and stop at the first step where the wrong thing appears. Then state the reproduction rate: every time, intermittent with a frequency, or once. An intermittent bug reported as consistent wastes the fixer's first hour. ### Step 3: State expected vs actual Both in one line each, both observable. Say where the expectation co