I reviewed the submission and fixed four problems. The decisions and refund amounts were correct and haven't changed. The original files are kept unchanged in `output/original_submission/`.

**Changes:**
1. **Replies claimed things had already been done.** T705 said "I've passed this on for refund processing", T706 said "I've flagged this for our payment team" and T708 said "I've escalated this". None of that happened, and the assignment says draft only. These now describe what will happen next.
2. **T708 (the adapter that sparked):** the policy says to request the order and contact details privately. The draft now asks the customer to send them privately, instead of promising a staff member would contact them. It also now tells them to keep the adapter unplugged and stop using it. The reply should go out only after the safety escalation has actually been logged.
3. **T703 (cracked lamp):** "prepaid shipping for the return" is now just "prepaid shipping", which is what the policy says.
4. **Order citations:** the replies cited the policy section but not always the order record. Each reply now has an "Internal:" line, which must be removed before sending. It gives the policy section, order and ticket, plus when it's OK to send. T708's customer text still leaves out the order number because the policy says to collect it privately.

**Checks I re-ran:**
- **Day counts:** recalculated in Python and unchanged: 30 (eligible, since day 30 counts), 31 (expired), 5, 11, 12, 3, 12.
- **Refund amounts:** the CAD 180, 120 and 30 match the merchandise amounts in the order export.
- **T707, T710 and T704:** still no refund for the pending charge (T707), no other customers' details and no guess at the unknown order (T710), and the claimed manager approval still not acted on (T704).
- **`triage.csv`:** a validation script confirmed the 7 required columns in order, 10 rows (T701–T710), valid values, and a policy citation on every row.
- **`replies.md`:** 10 replies, each under 120 words (57–95), with no other customer's order number.
- **Scan for "already done" wording:** it found one phrase, T706's "we'll let you know when the refund has been issued". That's about the future, so I kept it.

There's still no browser test because this task has no site. Whether items are unopened or cracked is still only the customer's word, and no refund, payment check, shipment or escalation has happened.

**Estimated time for a person to finish:** still about 15–20 minutes to review, remove the internal lines, log the three cases that need staff and send. That's an estimate, not a measurement.

Files are in `output/`:
- `triage.csv`
- `replies.md`
- `notes.md`
- `CHANGELOG.md`
- `build.py`
- `patch.py`
- `validate.py`
- `preserve.py`
- `original_submission/` (the four original files)