docs: add the operator and Site guides and bring the roadmap up to date

The operator guide covers the Kanban flow from quote review to finished
order; the Site guide walks through the customer journey, prices and the
current state of each integration. The roadmap records the Kanban and Site
redesigns, the guides, and what is left for the last day of Week 2.

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

docs/ROADMAP.md

@@ -7,16 +7,23 @@
 > Update the **Current step** line and the item status every time something moves.
 > Add new findings at the bottom of the relevant block rather than rewriting history.
 
-**Current step (2026-09-24, Week 2):** Client inputs for Mercado Pago and
-freight were requested on 2026-09-24; Tiny access is already with the client.
-Built without them: server-side print-file generation (1.4), the delivery
-address (3.8), the Kanban's payment-issue and print-file views (1.5), and
-Mercado Pago and Tiny adapters written from the public API documentation and
-tested against fake transports (1.1, 1.3). None of the provider work is a
-verified integration. The complete CI integration sequence passed locally on
-2026-09-24 (all API suites including the new `print_file_test`, adapter and
-generator unit suites, retention, runtime security, and both browser suites),
-run with Docker Engine in WSL against a fresh build; pending a Gitea runner run.
+**Current step (2026-09-25, last day of Week 2):** Still waiting on the client
+for Mercado Pago credentials and webhook access (1.1) and freight data (1.2);
+Tiny's app credentials are in production and the connection starts from the
+Kanban (1.3). Built and deployed without them: server-side print-file
+generation (1.4), the delivery address (3.8), the Kanban's payment-issue and
+print-file views and its redesign (1.5), the Site redesign (5.17), and Mercado
+Pago and Tiny adapters written from the public API documentation and tested
+against fake transports. None of the provider work is a verified integration.
+Every change passed the full integration sequence locally (Docker Engine in
+WSL) and on the Gitea runner, which publishes images on green pushes to `main`;
+the user verified each release in production after redeploying in Portainer.
+Operator and Site guides are in `docs/` (see Reporting).
+**Left for today:** product ids for the four products from the client's Tiny and
+one supervised real order (1.3); a Mercado Pago sandbox payment by PIX and card
+if the credentials arrive (1.1); the freight connector if the data arrives
+(1.2, otherwise the one Week 2 item that slips, on client inputs); the Week 2
+client report.
 
 **Previous step (2026-09-23):** Payment safety fixes 2.13 and 2.14 and
 the local order-correctness work in 3.6/3.9 have passed integration checks.
@@ -292,6 +299,12 @@ download, approve as final, queue; hand-preparation routing and retry).
   (`movements.back`), without notifying the customer; "production started" and
   "ready" are enqueued once per order. Previously the only way back was
   Correção, which messages the customer and invalidates approved finals.
+  **Redesign (2026-09-24):** tabs for Produção, Cotações, Pagamentos and
+  Integrações; an order panel with stages, items, print files, final files and
+  history; numbered pagination (20 per page) on quotes, payment issues and the
+  integration log, which also has filters; messages dismiss themselves. The
+  operator guide (`docs/guia-operador-kanban.pdf`) documents the flow for the
+  operation to confirm.
 - `[x]` 1.6 — **Block 0.2 + 0.3** were completed and verified on 2026-09-18.
 
 `[!]` The production compose currently blocks `dev_paid` (`ENVIRONMENT != 'local'`)
@@ -715,6 +728,22 @@ print-file evidence still need correction before this item can close.
   attempt counts against the source address and only failures count against
   the account; registration still counts every attempt. The security suite's
   lockout check (ten failures, then 429) is unchanged and passes.
+- `[x]` 5.17 — Site redesign (2026-09-24), Dropstar brand kept; the previous
+  look is tag `ui-v1`. The home, one page per product (`/arquivo-por-metro`,
+  `/artes-avulsas`, `/uv-arquivo-por-metro`, `/uv-artes-avulsas`) and
+  `/carrinho` have their own addresses but stay one document, so artwork held in
+  the browser survives moving between them (`web/site-pages.js`,
+  `web/site-steps.js`; nginx serves `index.html` for those paths). The product
+  page is built around a buy box (`web/site-compra.js`) that shows the item the
+  flow already priced (grade, price per metre, metres charged, total,
+  resolution acknowledgement and "Adicionar ao carrinho"); the duplicated
+  quality and preview panels are hidden. The cart has "Remover" per item,
+  "Esvaziar carrinho" and an 8-second undo. Fixed on the way, all already in
+  production before: the saved-cart note took a grid column and pushed the
+  order into a narrow strip, the panels outside `.w` ran edge to edge, and
+  "57 cm" wrapped on the ready-sheet option. The browser suite covers product
+  and cart addresses, reload on a product page, and remove/undo; the security
+  suite checks the new addresses carry the same CSP.
 - `[ ]` 5.13 — Define production recovery: scheduled encrypted offsite database
   and object backups, a consistent snapshot boundary, Swarm data placement and
   a restore rehearsal that opens every required live order file.
@@ -836,6 +865,12 @@ print-file evidence still need correction before this item can close.
 
 ### Reporting
 
+- `[x]` Operator guide (`docs/guia-operador-kanban.pdf`) and Site guide
+  (`docs/guia-site-dtf.pdf`), 2026-09-24, with screenshots of a throwaway stack
+  and fictional orders. The payment step has no screenshot until Mercado Pago
+  is configured, and the guides name the provisional Kanban domain; regenerate
+  them when either changes. Early work toward Week 3's "orientação à operação".
+- `[ ]` Week-2 client report, due end of day 2026-09-25.
 - `[x]` Week-1 client report (`Relatorio-Semana-1-DTF.docx`), corrected 2026-09-18 to
   remove the inaccurate "Arquivo por metro permanece separado, com seleção explícita"
   claim and the internal commit reference.