docs/Agent-folds-open · L-260924-98ae79

CHANGELOG.md

@@ -7,6 +7,10 @@
 - **The unit tests sweep the edit hook over the MTHDS Test Corpus**: `tests/data/mthds-corpus/` is a vendored copy of the whole corpus, and `tests/unit/test_hook_corpus.py` runs the hook's offline stages over every entry, expecting a block exactly when the entry's fault is one the schema catches and a silent pass otherwise. A vendored hook whose schema refuses a form the standard allows, the way the bundle before 0.8.0 refused intent hints, now fails the unit tests, and CI installs Node so that the sweep runs there rather than skips.
 - **A release refuses a stale hook bundle**: `make check-hook-fresh`, which the release skill now runs before anything else, fails when the vendored `check.mjs` embeds an older `@pipelex/tools-wasm` than npm's latest or when a rebuild in the `pipelex-sdk-js` checkout would change it, and names the re-vendor that cures it. `make check` separately refuses, in CI too, a bundle whose provenance names an unreleased engine or no SDK commit.
 
+### Changed
+
+- **The quick start shows both agents' installs**: the README's Codex install now starts open beside the Claude Code one instead of folded.
+
 ### Fixed
 
 - **The plugin says it needs Node.js**: the README and the Codex listing said the Pipelex tools needed nothing else to install, but the hook runs on Node.js and each agent starts the tools through `npx`, so without Node.js on the `PATH` the hook passes every edit unchecked and the skills that call the tools stop. The README, the Codex listing and each agent's install section now say that Node.js must be on the `PATH`.

README.md

@@ -27,7 +27,7 @@ Claude Code also loads what you have added to your Claude account, so if the Pip
 
 </details>
 
-<details><summary><b>Codex</b></summary>
+<details open><summary><b>Codex</b></summary>
 
 ```bash
 codex plugin marketplace add Pipelex/pipelex-plugins