Finish the rename in the prose

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

workflows/README.md

@@ -21,7 +21,7 @@ POST  /rest/workflows/<id>/activate     {"versionId": "<current>"}
 `PATCH {"active": true}` returns 200 and leaves the workflow inactive, silently:
 activation has its own endpoint.
 
-## approvisionnement-check-availability
+## supply-check-availability
 
 Working. `POST /webhook/check-availability` with the end user's token in
 `X-Subject-Token`:
@@ -156,7 +156,7 @@ threshold, from 68" reads as a contradiction even though both halves are true,
 so the context is appended only while the reference is actually below the
 threshold.
 
-## approvisionnement-periodic-reorder
+## supply-periodic-reorder
 
 The periodic half. A schedule trigger at 06:00, deliberately periodic rather
 than a batch standing in for events: grouping references into a purchase
@@ -215,7 +215,7 @@ the output. A catalog that outgrows one page needs a paging loop **and** the
 read-volume cap this repo already lists as mandatory for autonomous agents.
 
 
-## approvisionnement-stock-watch
+## supply-stock-watch
 
 The reactive half, and the one the design had been waiting on. It is woken by
 `product.stock_changed` on `classic-models.catalog` rather than by a clock, so a
@@ -274,7 +274,7 @@ better answer when it knows X crossed the threshold at 14:32.
   explicitly and succeeds. A workflow that threw on an uninteresting event would
   replay it forever.
 - The consumer has its **own** SCRAM account,
-  `classic-models-agent-approvisionnement`: Read on that one topic and that one
+  `classic-models-agent-supply`: Read on that one topic and that one
   consumer-group prefix. It cannot read sales or payments, and it cannot write —
   so a compromised workflow can raise no event another agent would act on.