lint(standard): corrections completes mode standard

- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)

wiki/modules/dom.md

@@ -44,13 +44,13 @@ Easy DOM is a Distributed Order Management platform that orchestrates the supply
 
 DOM centralizes visibility of inventory across the entire organization network and applies configurable orchestration strategies to assign each sales order to the best possible supply point based on proximity, stock availability, carrier availability, and work capacity.
 
-DOM integrates with the ERP (source of purchase/sales orders) and with each node's WMS (Easy WMS or compatible systems that communicate via standard messaging). It does not execute warehouse operations directly — it delegates to the nodes.
+DOM integrates with the ERP (source of purchase/sales orders) and with each node's WMS (Easy WMS or compatible systems that communicate via standard messaging). It does not execute warehouse operations directly - it delegates to the nodes.
 
 ## Key capabilities
 
 - Multi-node inventory visibility: stock levels aggregated across all organization nodes (org level, node level, line level)
 - Outbound orchestration: 5-stage algorithm assigns each sales order to the optimal fulfillment node
-- Inbound centralization: purchase orders from ERP distributed to nodes as receipt orders (no orchestration — node assignment is direct)
+- Inbound centralization: purchase orders from ERP distributed to nodes as receipt orders (no orchestration - node assignment is direct)
 - Inter-node replenishment: replenishment orders move stock between nodes to maintain capacity levels
 - Node network configuration: sourcing relationships, geographic regions, carrier assignments, workload limits
 - Master data management: owners, items, suppliers, carriers, accounts, account types, geographic regions, kits
@@ -150,7 +150,7 @@ Available for orders in _Pending_ status (no assigned stock). Step-by-step:
 2. Select available nodes for each line
 3. Assign stock quantities per line (partial assignment allowed)
 4. Review shipping orders to be created (can change ship date or carrier)
-5. Confirm — shipping orders created
+5. Confirm - shipping orders created
 
 If stock becomes unavailable during the wizard (concurrent assignment), the order is released with _Incomplete_ or _Assignment error_ status.
 
@@ -165,7 +165,7 @@ Reorchestration priority criteria:
 4. Order release date
 5. Order creation date
 
-**Parameter**: `MAX_NUMBER_ORCHESTRATION_ATTEMPS_AFTER_REJECTIONS` — limits how many times an order is reorchestrated after node rejections; notifies when limit is reached.
+**Parameter**: `MAX_NUMBER_ORCHESTRATION_ATTEMPS_AFTER_REJECTIONS` - limits how many times an order is reorchestrated after node rejections; notifies when limit is reached.
 
 Orders exceeding maximum deliveries or whose committed date cannot be met with any reorchestration cannot be automatically reorchestrated and must be manually closed (incomplete).
 
@@ -175,7 +175,7 @@ If no single node can ship the complete order, DOM can assign parts to multiple
 
 ## Inbound: Purchase Order Management
 
-DOM does not orchestrate inbound — it records and distributes purchase orders to nodes based on order line data.
+DOM does not orchestrate inbound - it records and distributes purchase orders to nodes based on order line data.
 
 ```
 ERP sends POR → DOM creates purchase order
@@ -190,7 +190,7 @@ ERP sends POR → DOM creates purchase order
 
 Receipt orders are read-only after creation; they update automatically based on purchase order edits. Receipt orders cannot be manually created.
 
-**Expected stock**: pre-notified stock visible in stock views as _receipt pending_ — can be used for backordering decision-making but is not available for orchestration assignment (backordering not currently supported).
+**Expected stock**: pre-notified stock visible in stock views as _receipt pending_ - can be used for backordering decision-making but is not available for orchestration assignment (backordering not currently supported).
 
 ## Replenishment: Inter-node Stock Movement
 
@@ -203,7 +203,7 @@ ERP/manual creates replenishment order
 → Replenishment order closes
 ```
 
-Automatic replenishment by safety stock breakage is **not currently supported** — replenishment orders must be created manually or by ERP.
+Automatic replenishment by safety stock breakage is **not currently supported** - replenishment orders must be created manually or by ERP.
 
 **Node sourcing relationships** (node network): defines which nodes can supply which other nodes, with priorities when multiple sources exist.
 
@@ -263,10 +263,10 @@ Per node:
 
 ## Related
 
-- [[order-inbound]] — Receipt orders are the WMS counterpart of DOM purchase orders
-- [[order-outbound]] — Shipping orders are the WMS counterpart of DOM sales orders
-- [[stock]] — DOM inventory visibility aggregates WMS stock across all nodes
-- [[replenishment]] — DOM node replenishment triggers inter-node stock movements
-- [[multi-carrier]] — Carrier assignments at DOM node level align with Multi-Carrier configuration at WMS level
-- [[store-fulfillment]] — Store nodes in DOM correspond to Store Fulfillment remote stores
-- [[yard-management]] — Inbound appointment management at nodes aligns with DOM purchase order arrival notifications
+- [[order-inbound]] - Receipt orders are the WMS counterpart of DOM purchase orders
+- [[order-outbound]] - Shipping orders are the WMS counterpart of DOM sales orders
+- [[stock]] - DOM inventory visibility aggregates WMS stock across all nodes
+- [[replenishment]] - DOM node replenishment triggers inter-node stock movements
+- [[multi-carrier]] - Carrier assignments at DOM node level align with Multi-Carrier configuration at WMS level
+- [[store-fulfillment]] - Store nodes in DOM correspond to Store Fulfillment remote stores
+- [[yard-management]] - Inbound appointment management at nodes aligns with DOM purchase order arrival notifications