docs(llm-helper): the Node twin lives in extensions/llm-helper too

CHANGELOG.md

@@ -58,7 +58,8 @@
    passes `--config`, or moves the folder next to the file.
 2. **The LLM helper graduates from an example to an extension: `extensions/llm-helper/`.** It is no longer a sample to copy
    but a function host an installation runs to give its engines an LLM, so it moves out of `examples/`, which keeps the
-   demo app. The files, the routes, the contract and the configuration keys are unchanged; the sdist ships the new folder.
+   demo app - in lockstep with the Node twin (mercury-nodejs #114). The files, the routes, the contract and the
+   configuration keys are unchanged; the sdist ships the new folder.
    **Upgrade note:** start it as `mercury-serve extensions/llm-helper/llm_helper.py` (or
    `python extensions/llm-helper/llm_helper.py`); a script or a deployment that names the old path changes it.
 

extensions/llm-helper/README.md

@@ -14,8 +14,9 @@ model advises within it.
 
 `llm.chat` is also the model turn of the engines' agent loop (`llm.run`): see The loop contract.
 
-The Node.js twin ([mercury-nodejs `examples/llm-helper`](https://github.com/Accenture/mercury-nodejs))
-speaks the same contract. Both run the same shared vector files, so they cannot drift apart.
+The Node.js twin ([mercury-nodejs `extensions/llm-helper`](https://github.com/Accenture/mercury-nodejs/tree/main/extensions/llm-helper))
+speaks the same contract. Both run the shared `llm-helper-vectors.json`, so they cannot drift apart; the twin's loop
+contract, on the shared `llm-loop-vectors.json`, is still to come.
 
 ## Run it
 

extensions/llm-helper/llm_helper.py

@@ -15,7 +15,7 @@
 llm.timeout.ms, llm.max.retries, llm.fallbacks, llm.effort, and for the agent loop's turns
 llm.transcript.store (memory or redis), llm.transcript.ttl, llm.transcript.retention and the
 llm.transcript.redis.* connection keys. The contract, the keys and the backends are documented in
-README.md next to this file. The Node.js twin (mercury-nodejs examples/llm-helper) speaks
+README.md next to this file. The Node.js twin (mercury-nodejs extensions/llm-helper) speaks
 the same contract, and both are pinned by shared vector files.
 
 Then map the routes from a Mercury engine application (event-over-http.yaml):