# Qwen — Word documents, raw output

- Date: 2026-09-19, sent 10:40 (+07), answered in about five minutes. Free, "Qwen3.7-Plus", "Авто" mode, interface Russian, answer in English. The composer's own upload input never attached the file (as in the meeting-notes test); a synthetic drop of the same file on the composer produced the chip "policy-dr… .docx 37.2 KB · Анализ…" and the send went through. Brief pasted.
- Capture: page text via the extension and screenshots. The chat opened in Qwen Studio's A/B mode ("Какой ответ вы предпочитаете?"): Answer 1 ran for four minutes and died with "Oops! There was an issue connecting to Qwen3.7-Plus. Internal Error"; Answer 2 finished and is what is scored (the operator picked it to continue, since it was the only one). **No file.** The answer ends with a link "Quinta_da_Ribeira_Shipping_and_Returns_Policy.docx ↗" that has no destination - the code saved to `/mnt/data/` inside its sandbox and the link is rendered with an empty href; four clicks (two by hand, two by script) opened nothing and downloaded nothing. `2/2` at the foot of the answer.
- First read: a 223-line python-docx script shown in full, then a "What I did" table with seven rows. From the code: Heading 1 sections numbered 1–8, a real TOC field with a "Right-click here and select Update Field" placeholder, a 5 × 4 table with all prices, all eight typos, the duplicate kept once in §2, a Title heading "Quinta da Ribeira — Shipping and Returns Policy" with "Valid from 1 July 2026". One change the brief did not ask for and it announces: "Last updated 07/01/2026" rewritten as "01/07/2026" to match the title date - a guess at which of the two the draft meant. Not scorable as a file; the code reads as though it would have produced a good one.

## Answer

[Завершено размышление]

[python — 223 lines shown, ending:]
    # --- Footer note ---
    doc.add_paragraph()
    footer_p = doc.add_paragraph()
    footer_p.alignment = WD_ALIGN_PARAGRAPH.RIGHT
    run = footer_p.add_run("Last updated 01/07/2026")
    set_run(run, size=9, color=(130, 130, 130))
    # --- Save ---
    output_path = "/mnt/data/Quinta_da_Ribeira_Shipping_and_Returns_Policy.docx"
    doc.save(output_path)
    print(f"Saved to {output_path}")

Here's your cleaned-up policy document: Quinta_da_Ribeira_Shipping_and_Returns_Policy.docx ↗

What I did

| Issue | Fix |
|---|---|
| Inconsistent numbering (1., Section 2 -, 3), 4, Refunds (6)) | All headings now use a uniform 1. – 8. scheme with Word Heading 1 style |
| Spelling errors | recieve → receive, seperate → separate, adress → address, wich → which, occassionally → occasionally, untill → until, definately → definitely, guarentee → guarantee |
| Duplicate paragraph | The "Shipping is free on orders over €60 … two parcels on the same day" block appeared in both §2 and §3; kept it only in §2 |
| Shipping rates | Converted to a proper Word table with a shaded header row and alternating row tints |
| Table of Contents | Inserted a live TOC field at the top — right-click it in Word and choose Update Field to populate it |
| Heading styles | Uses built-in Heading 1 / Heading 2 styles so the TOC and Navigation Pane work automatically |
| Date format | The "Last updated" line was 07/01/2026 (ambiguous); changed to 01/07/2026 to match the "valid from 1 July 2026" in the title |

All amounts, timeframes, and policy rules are unchanged. Open the file in Word, update the TOC, and you're good to go!

[Answer 1, the other half of the A/B pair: "Oops! There was an issue connecting to Qwen3.7-Plus. Internal Error" after four minutes of "Refining the document structure by eliminating redundancy…"]