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)
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
@@ -26,18 +26,18 @@ The AD contains approximately **38,765 elements** spanning Commands, Queries, Di

 ### Commands

-Commands represent **executable operations** — actions that change system state.
+Commands represent **executable operations** - actions that change system state.

 - Mapped to `POST /api/commands/{commandName}` in the API
 - Have input parameters (validated before execution) and return a result
 - May trigger Transactions (audit records) and Events
 - May invoke sub-commands or start Workflows
 - Examples:
-  - `ReceiveContainer` — receive a container at a dock station
-  - `ReleaseShippingOrder` — release a shipping order for picking
-  - `AdjustStock` — perform a quantity adjustment
-  - `CreateCount` — create a physical count order
-  - `AssignTask` — assign a task to an operator
+  - `ReceiveContainer` - receive a container at a dock station
+  - `ReleaseShippingOrder` - release a shipping order for picking
+  - `AdjustStock` - perform a quantity adjustment
+  - `CreateCount` - create a physical count order
+  - `AssignTask` - assign a task to an operator

 Commands are permission-controlled: each command is associated with one or more AD roles. A user can only execute commands their role permits.

@@ -49,16 +49,16 @@ Queries represent **data retrieval operations** using a LINQ-style expression en
 - Support filtering, sorting, pagination
 - Can reference any View or Entity
 - Examples:
-  - `GetStockByLocation` — fetch stock for a location
-  - `GetOpenShippingOrders` — fetch all non-closed shipping orders
-  - `GetContainerContents` — fetch stock lines in a container
-  - `GetTasksByStatus` — fetch tasks matching a status
+  - `GetStockByLocation` - fetch stock for a location
+  - `GetOpenShippingOrders` - fetch all non-closed shipping orders
+  - `GetContainerContents` - fetch stock lines in a container
+  - `GetTasksByStatus` - fetch tasks matching a status

 The **QueryExecute API** allows ad-hoc LINQ queries without pre-defining a named Query element.

 ### Entities

-Entities are the **core data objects** of the system — the persistent domain model.
+Entities are the **core data objects** of the system - the persistent domain model.

 Each Entity has:
 - A schema (fields, types, constraints)
@@ -111,11 +111,11 @@ Views are **read-only projections** of one or more Entities, optimized for displ
 - May include computed columns and aggregations
 - Back all SmartUI list screens and RF terminal display screens
 - Examples:
-  - `ViewContainers` — containers with location and status
-  - `ViewStocks` — stock lines with full context
-  - `ViewTasksOpen` — open tasks with assignment info
-  - `ViewShippingOrdersMonitor` — order monitoring dashboard
-  - `ViewGroupedStock` — aggregated stock by item/owner
+  - `ViewContainers` - containers with location and status
+  - `ViewStocks` - stock lines with full context
+  - `ViewTasksOpen` - open tasks with assignment info
+  - `ViewShippingOrdersMonitor` - order monitoring dashboard
+  - `ViewGroupedStock` - aggregated stock by item/owner

 ### Dialogs

@@ -126,10 +126,10 @@ Dialogs are **multi-step interactive flows** that guide an operator through a co
 - State is maintained server-side between steps
 - API: `POST /api/dialogs/{dialogName}/start`, then `POST /api/dialogs/{sessionId}/step`
 - Examples:
-  - `ReceptionDialog` — multi-step reception flow (select order → scan container → enter quantities → confirm)
-  - `PickingDialog` — guided picking (scan location → confirm quantity → scan destination)
-  - `CountDialog` — count guided flow (scan location → count items → confirm)
-  - `ShippingConsolidationDialog` — consolidation at shipping station
+  - `ReceptionDialog` - multi-step reception flow (select order → scan container → enter quantities → confirm)
+  - `PickingDialog` - guided picking (scan location → confirm quantity → scan destination)
+  - `CountDialog` - count guided flow (scan location → count items → confirm)
+  - `ShippingConsolidationDialog` - consolidation at shipping station

 Dialogs encapsulate the complete operator interaction sequence for a process, invoking Commands internally at each confirmation step.

@@ -155,11 +155,11 @@ Workflows are **orchestrated sequences** of Commands, conditional logic, and sta
 - Used for complex multi-step processes: reception, putaway strategy evaluation, replenishment logic
 - Can be synchronous (blocking) or asynchronous (background)
 - Examples:
-  - `PutawayWorkflow` — 8-stage pipeline (criteria → aisles → balancing → restrictions → validity → rules → sort → select)
-  - `StockAssignmentWorkflow` — evaluate assignment strategies → assign to shipping order lines
-  - `ReplenishmentWorkflow` — check PDL levels → select strategy → generate tasks
-  - `DefragmentationWorkflow` — evaluate rotation/shipping criteria → generate movement tasks
-  - `CountCloseWorkflow` — close count → compute differences → generate STK.ADJ transactions → send COF to ERP
+  - `PutawayWorkflow` - 8-stage pipeline (criteria → aisles → balancing → restrictions → validity → rules → sort → select)
+  - `StockAssignmentWorkflow` - evaluate assignment strategies → assign to shipping order lines
+  - `ReplenishmentWorkflow` - check PDL levels → select strategy → generate tasks
+  - `DefragmentationWorkflow` - evaluate rotation/shipping criteria → generate movement tasks
+  - `CountCloseWorkflow` - close count → compute differences → generate STK.ADJ transactions → send COF to ERP

 ### Background Jobs

@@ -178,7 +178,7 @@ Background Jobs are **scheduled or continuous Workflows** that run autonomously:

 ### Parameters

-AD Parameters are the **configuration knobs** of the system — named key-value pairs that alter behavior without code changes.
+AD Parameters are the **configuration knobs** of the system - named key-value pairs that alter behavior without code changes.

 - Scope: Organization or Warehouse
 - Accessible via the Parameters view in SmartUI (Inventory > Parameters)
@@ -238,12 +238,12 @@ The AD can be extended by Mecalux partners:
 4. **Custom Parameters**: Add module-specific configuration
 5. **Custom Events**: React to standard system events with custom logic

-This extensibility model is used by all optional modules (AGV, Slotting, 3PL Billing, DOM, etc.) — each module adds its own AD elements without modifying core elements.
+This extensibility model is used by all optional modules (AGV, Slotting, 3PL Billing, DOM, etc.) - each module adds its own AD elements without modifying core elements.

 ## Related

- [Overview](overview.md) — System architecture and deployment
- [Entities Map](entities-map.md) — Visual map of entity relationships
- [Transactions](../concepts/transactions.md) — Transaction audit trail (generated by Commands)
- [ERP Interface](../concepts/erp-interface.md) — ERP messages (triggered by Events)
- [Parameters](../concepts/parameters.md) — System parameter catalog
+- [Overview](overview.md) - System architecture and deployment
+- [Entities Map](entities-map.md) - Visual map of entity relationships
+- [Transactions](../concepts/transactions.md) - Transaction audit trail (generated by Commands)
+- [ERP Interface](../concepts/erp-interface.md) - ERP messages (triggered by Events)
+- [Parameters](../concepts/parameters.md) - System parameter catalog