Eliminar payment + waiting (legacy): el bot toma pedidos, no cobra

El bot conversacional no maneja pagos. Su trabajo: pedidos, datos de
entrega, dejar la orden anotada en Woo (status=pending). El cobro lo
gestiona el comercio offline. Todo lo de payment_type / is_paid /
PAYMENT / WAITING_WEBHOOKS era legacy de un flow viejo que se baja.

Nuevo flow: IDLE → CART → SHIPPING → IDLE (con orden creada).
Cuando el usuario completa shipping (pickup elegido OR delivery+address),
shipping.js emite create_order y el bot cierra con order.confirmed.

- fsm.js: 4 estados (IDLE/CART/SHIPPING/AWAITING_HUMAN). hasPaymentInfo
  e isPaid eliminados. deriveNextState gira SHIPPING→IDLE en vez de
  →PAYMENT→WAITING. ALLOWED transitions actualizadas.
- orderModel.js: createEmptyOrder() sin payment_type/is_paid.
  migrateOldContext deja de leer payment_method / mp.payment_status.
- stateHandlers: payment.js y waiting.js eliminados. shipping.js gana
  finalizeOrder() que emite create_order action y vuelve a IDLE.
- replyTemplates: payment.* y waiting.* fuera. order.confirmed nuevo,
  con 3 variantes y rewriter habilitado.
- NLU openai.js + nlu/schemas.js: select_payment fuera del enum, payment_method
  fuera de entities. Prompt sin la regla de SELECCIONAR PAGO.
- nlu/router.js + nlu/index.js: dominio "payment" eliminado.
  shouldSkipRouter ya no chequea PAYMENT.
- nlu/specialists/payment.js: eliminado.
- promptsRepo.js + promptLoader.js: PROMPT_KEYS sin "payment".
- turnEngineV3.js: switch ya no dispatcha a PAYMENT/WAITING. normalizeState
  mapea estados legacy (PAYMENT/WAITING_WEBHOOKS/COMPLETED) a IDLE.
  context_patch ya no emite payment_method.
- wooOrders.createOrder: paymentMethod param eliminado. Order queda en
  status=pending sin payment_method (cobro offline).
- pipeline.js: paymentMethod fuera del create_order glue. Invariant
  "no_checkout_without_payment_link" eliminado. signal payment_selected
  reemplazado por shipping_completed.
- XState machine: top-level PAYMENT y WAITING eliminados. SELECT_PAYMENT
  event fuera. SHIPPING ahora cierra con enqueueWooCreateOrder +
  replyOrderConfirmed → IDLE. Guards hasPayment/isPaid borrados.
- Tests fsm.test.js / orderModel.test.js / machine/index.test.js
  actualizados al nuevo contrato. 188 tests pasando.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

src/modules/4-woo-orders/wooOrders.js

@@ -193,27 +193,23 @@ function mapAddress(address) {
   };
 }
 
-export async function createOrder({ tenantId, wooCustomerId, basket, address, shippingMethod, paymentMethod, run_id }) {
+export async function createOrder({ tenantId, wooCustomerId, basket, address, shippingMethod, run_id }) {
   const lockKey = `${tenantId}:${wooCustomerId || "anon"}`;
   return withLock(lockKey, async () => {
     const client = await getWooClient({ tenantId });
     const lineItems = await buildLineItems({ tenantId, basket });
     if (!lineItems.length) throw new Error("order_empty_basket");
     const addr = mapAddress(address);
+    // Estado "pending" en Woo = el pago/cobro lo gestiona el comercio offline.
     const payload = {
       status: "pending",
       customer_id: wooCustomerId || undefined,
       line_items: lineItems,
       ...(addr ? { billing: addr, shipping: addr } : {}),
-      // Si es cash, usar payment_method "cod" (Cash On Delivery) de WooCommerce
-      ...(paymentMethod === "cash" ? { payment_method: "cod", payment_method_title: "Efectivo" } : {}),
       meta_data: [
         { key: "source", value: "whatsapp" },
         ...(run_id ? [{ key: "run_id", value: run_id }] : []),
-        // Guardar shipping_method como metadata para poder leerlo después
         ...(shippingMethod ? [{ key: "shipping_method", value: shippingMethod }] : []),
-        // Guardar payment_method como metadata también
-        ...(paymentMethod ? [{ key: "payment_method_wa", value: paymentMethod }] : []),
       ],
     };
     const url = `${client.base}/orders`;