Explain a SQL query before you reuse or change it

Database or tool it runs in: {{database}}
What I was told the query does: {{stated_purpose}}
What I want to change, if anything: {{change_wanted}}
My SQL level: {{sql_level}}

The query:
"""
{{query}}
"""

Notes on the tables and columns, if I have them (what each table holds, what one row is):
"""
{{schema_notes}}
"""

Task:
Explain the query above in plain words, so that I can reuse it with confidence and make the change I described without breaking it.

Format:
1. In one paragraph: what one row of the result is, what each column means, and which records are included and left out.
2. Part by part: walk through the query in the order the database runs it (FROM and JOINs, WHERE, GROUP BY, HAVING, SELECT, ORDER BY), quoting each piece and explaining it in one or two sentences.
3. Things that could make the numbers wrong: for example a join that can repeat rows and double count, a filter that drops rows with blank values, a hard-coded date, a time zone, or COUNT(*) where COUNT(DISTINCT ...) was meant. For each, say whether it applies here and how to check, such as counting rows before and after a join.
4. My change: the edited query in a code block, with each changed line marked by a comment, and anything else that might need to change with it.
5. A quick test: one simple query or check to confirm the edited version returns what I expect.

Requirements:
- Under 500 words, plus code.
- Do not assume what a table or column holds beyond its name and my notes; when you must, say it, for example "assuming orders has one row per order".
- Keep the {{database}} dialect, and point out any function specific to it.
- Change nothing I did not ask to change.

Example of one part-by-part line's form only: "LEFT JOIN refunds r ON r.order_id = o.id: keeps every order and adds refund details where they exist; an order with two refunds appears twice."

If what I was told the query does does not match what it actually does, say so first, plainly.