feat: price home delivery with Jadlog

FREIGHT_ADAPTER=jadlog prices "Receber em casa" through Jadlog's Simulador
de Frete from the order's billed metres and value, adding production days
to Jadlog's delivery time. The package weight is a base plus a weight per
metre from the client, with no default: the adapter refuses to start
without it and without the credentials. The cart re-quotes when the package
changes, and approval quotes again from the server-priced items. The
production stack takes the Jadlog settings, so the read-only probe runs
from the worker's console.

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

docs/ROADMAP.md

@@ -265,6 +265,15 @@ From the report already sent. These are dated promises, not backlog.
   2026-09-28). `app/jadlog.py` prices one package from the manual (v2.3);
   `python -m app.jadlog_probe` prices test weights to six regions, read-only,
   to confirm token, account and contract on the client's account. Not yet run.
+  **Adapter (2026-09-29):** `FREIGHT_ADAPTER=jadlog` prices "Receber em casa"
+  with Jadlog from the order's billed metres (`JADLOG_PESO_BASE_KG` plus
+  `JADLOG_PESO_POR_METRO_KG` per metre) and value, adds
+  `FREIGHT_PRODUCTION_DAYS` to Jadlog's time, re-quotes the cart when it
+  changes, and quotes again at approval from the priced items. It refuses to
+  start without the credentials and the weights, which have no default. The
+  production stack now takes the Jadlog settings, so the probe runs from the
+  worker's console. Cubed weight is not computed: the client's box sizes will
+  tell whether it is needed.
 - `[~]` 1.3 — Idempotent Tiny/Olist order creation with order-number traceability.
   Confirm endpoints, tag behaviour and rate limits first.
   **Groundwork (2026-09-24), API v3 by decision:** OAuth2 against Tiny's