feat: approve priced carts at checkout so customers can pay at once

Every quote waited for an operator before it could be paid, so an order
placed at night waited for the morning. A cart the Site priced is now
approved when the quote is created, through the same server pricing the
operator's approval uses (app/quote_review.py). Orders above
QUOTE_AUTO_MAX_METRES (50 m) and items claiming a discount on art the Site
could not analyse still wait for review; the Kanban shows which quotes were
approved automatically and why the others wait.

The grade is still computed in the browser (roadmap 3.2, 3.9), so the
discount remains a customer-supplied value until the server computes it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/ROADMAP.md

@@ -579,7 +579,19 @@ The production topology has not been verified by the repository review.
 
 ## Block 3 · Architecture — needs a decision before code
 
-### `[?]` 3.1 — Manual quote approval contradicts the 24h business case `(F16)`
+### `[~]` 3.1 — Manual quote approval contradicts the 24h business case `(F16)`
+
+**Decided 2026-09-28 (the user: "we are an e-commerce"):** a cart the Site
+priced is approved when the quote is created and can be paid at once
+(`app/quote_review.py`, the same pricing the operator's approval uses). A
+person reviews only orders above `QUOTE_AUTO_MAX_METRES` (50 m) and items
+that claim a grade the Site could not have computed (unanalysed art with a
+discount). The Kanban lists automatic approvals and the reason for each
+manual one. **Still open:** the grade and layout are the browser's (3.2,
+3.9), so a customer who edits the page can claim a better grade, up to the
+top tier's discount; the server must compute the grade before this closes.
+
+Previously:
 
 Payment requires `quotes.approved`, set only by an authenticated operator. The
 meeting's premise was that the 17h30 order waiting until 5am is what costs the