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/concepts/task.md

@@ -85,17 +85,17 @@ In **automatic warehouses**, tasks are executed by automated systems (AS/RS, AGV
         ↓
    Task CREATED (pending movement generation)
         ↓
-   PENDING — waiting for movement to be generated
+   PENDING - waiting for movement to be generated
         ↓
-   GENERATED — movement created, no operator/machine assigned yet
+   GENERATED - movement created, no operator/machine assigned yet
         ↓
-   IN PROCESS — currently being executed
+   IN PROCESS - currently being executed
         ↓
-   FINISHED — task completed successfully
-   
+   FINISHED - task completed successfully
+
    (at any point from Generated or In Process)
         ↓
-   CANCELED — task stopped by user action
+   CANCELED - task stopped by user action
 ```
 
 ### Status transitions
@@ -110,7 +110,7 @@ In **automatic warehouses**, tasks are executed by automated systems (AS/RS, AGV
 
 ## Tasks and movements
 
-The task defines **from where to where** (source station → destination station). The actual path may pass through multiple intermediate stations. Easy WMS decomposes the task into **movements** — each movement covers one segment (one station to the next).
+The task defines **from where to where** (source station → destination station). The actual path may pass through multiple intermediate stations. Easy WMS decomposes the task into **movements** - each movement covers one segment (one station to the next).
 
 Each segment has a configured **manager** (who/what executes it):
 - **RF**: human operator with radio frequency terminal
@@ -133,7 +133,7 @@ Movement release (reset In Execution → Pending) is available for resolving inc
 ## Business rules
 
 - **Cannot manually complete** picking, counting, replenishment (stock replenishment type), kit assembly, or consolidation tasks. These must be completed through their respective processes.
-- **Task assignment** to user or equipment respects work zone restrictions — if the equipment cannot access the required work zone or aisle, the task will not be executable.
+- **Task assignment** to user or equipment respects work zone restrictions - if the equipment cannot access the required work zone or aisle, the task will not be executable.
 - **Equipment incompatibility**: equipment that cannot transport the container type specified in the task is ineligible.
 - **Priority** drives task sequencing within a process queue (lower number = higher priority; values: Very Low, Low, Normal, High, Urgent).
 - **Task cancellation**: container stays where the operator reports it (user must indicate the location, including position for rack locations or depth for channel locations).
@@ -152,7 +152,7 @@ For manual warehouse RF execution, the priority ordering is:
 
 **Shipping tasks:** Round number → Priority → Empty channel → Stackability → Distance → Creation date
 
-**Wave picking:** Priority (of the wave/orders assigned) → Route path (right and left sides, low to high — no second rounds)
+**Wave picking:** Priority (of the wave/orders assigned) → Route path (right and left sides, low to high - no second rounds)
 
 **Order picking (RF):** For task selection: assigned to user/equipment first → Priority → Release date. For task execution: same as automatic tasks.
 
@@ -201,16 +201,16 @@ Transactions are generated by the underlying process (not by semi-automatic mode
 | Task created but not assignable | Equipment type incompatible with container type in task | Assign different equipment; check equipment container type configuration |
 | Task cannot be manually completed | Task type is picking, counting, stock replenishment, kit assembly, or consolidation | Complete via the appropriate process screen (picking station, count screen, etc.) |
 | Movement stuck In Execution | Automatic system malfunction or communication failure | Use Movement Release to reset to Pending; investigate automation incident |
-| Canceled task — container not found | Operator reported wrong location at cancellation | Run a count or check Last Known Location; resolve via Lost & Found if needed |
+| Canceled task - container not found | Operator reported wrong location at cancellation | Run a count or check Last Known Location; resolve via Lost & Found if needed |
 | Task not generated after process trigger | Work zone restriction prevents any available equipment from executing | Check work zone configuration and available equipment |
 
 ## Related
 
-- [[location]] — tasks always have a source and destination location; location type (rack, compact, etc.) determines coordinate precision in tasks
-- [[container]] — most automatic warehouse tasks move containers; task references container code and type
-- [[stock]] — stock tasks (picking, replenishment) specify item, quantity, and logistic attributes
-- [[putaway]] — putaway process generates Putaway tasks; PIE/MU/TRL/ALM stations trigger automatic task creation
-- [[picking]] — picking process generates Picking tasks; wave/group picking generates batches of tasks
-- [[shipping]] — shipping process generates Shipping and Loading tasks for consolidation and dock delivery
-- [[replenishment]] — replenishment generates Container replenishment or Stock replenishment tasks to PDLs
-- [[count]] — count processes generate Location count, Container count, or Item count tasks
+- [[location]] - tasks always have a source and destination location; location type (rack, compact, etc.) determines coordinate precision in tasks
+- [[container]] - most automatic warehouse tasks move containers; task references container code and type
+- [[stock]] - stock tasks (picking, replenishment) specify item, quantity, and logistic attributes
+- [[putaway]] - putaway process generates Putaway tasks; PIE/MU/TRL/ALM stations trigger automatic task creation
+- [[picking]] - picking process generates Picking tasks; wave/group picking generates batches of tasks
+- [[shipping]] - shipping process generates Shipping and Loading tasks for consolidation and dock delivery
+- [[replenishment]] - replenishment generates Container replenishment or Stock replenishment tasks to PDLs
+- [[count]] - count processes generate Location count, Container count, or Item count tasks