docs: le pair optionnel @ng-org/orm dit ce que pnpm fait vraiment

Les deux textes expliquaient que `bun install` ne va pas chercher le pair
optionnel. Mesure : pnpm ne le va pas chercher non plus pour un consommateur
qui ne le nomme pas (un paquet qui ne declare que le polyfill recoit zero
@ng-org, sans avertissement) - mais ce depot-ci l-obtient quand meme, parce
que `packages/polyfill` le declare aussi en devDependency. Un `pnpm install`
depuis un `node_modules` vide suffit donc a faire construire le bundle du
runner, et le message qui demandait d-installer l-ORM a la main etait devenu
un faux conseil.

.project/concepts/e2e-harness/knowledge_what-each-suite-judges.md

@@ -11,7 +11,7 @@ summary: Which suite answers which question, what a batch costs, and why two run
 
 **The reactivity suite** isolates document subscription.
 
-**The ORM live-read measurement** asks one question of the deployment rather than of this package: does a live `useShape` read actually start. It is the only runner that imports `@ng-org/orm` — an optional peer `bun install` does not fetch — which is why it stands apart from the polyfill suite instead of inside it: a checkout without the ORM must still be able to run the other three. It exited non-zero for as long as the deployed broker and the published client packages disagreed on `orm_start_graph`; since the packages caught up on 2026-09-21 it is GREEN, and a red run now means they have drifted apart again.
+**The ORM live-read measurement** asks one question of the deployment rather than of this package: does a live `useShape` read actually start. It is the only runner that imports `@ng-org/orm`, which the polyfill declares an OPTIONAL PEER - so an application that does not name the ORM gets nothing, and a checkout without the ORM must still be able to run the other three, which is why this runner stands apart from the polyfill suite instead of inside it. It exited non-zero for as long as the deployed broker and the published client packages disagreed on `orm_start_graph`; since the packages caught up on 2026-09-21 it is GREEN, and a red run now means they have drifted apart again. Do not read the optional peer as "this checkout has no ORM": `packages/polyfill` also lists it in its devDependencies, so `pnpm install` here fetches it and the runner's bundle builds with no extra step - measured 2026-09-24 by installing from an empty `node_modules`. The optional peer governs what a CONSUMER receives, not what this repository installs.
 
 A unit suite cannot replace any of the first three, and none of them replaces the unit suite: they are slow, they depend on live external services, and they cannot enumerate a case space.
 

packages/polyfill/e2e/orm-live-read.ts

@@ -156,8 +156,10 @@ async function main(): Promise<void> {
   } catch (e) {
     console.error(
       "[orm-live] the bundle did not build. `@ng-org/orm` is an OPTIONAL PEER of this " +
-        "package and `bun install` does not fetch it — install it in packages/polyfill " +
+        "package, so an application that does not name it gets nothing - but THIS " +
-        "before running this measurement. NOTHING was measured, so nothing is concluded.",
+        "checkout declares it in packages/polyfill devDependencies, and `pnpm install` " +
+        "does fetch that. So the ORM is not missing by design here: run `pnpm install` " +
+        "at the repository root. NOTHING was measured, so nothing is concluded.",
     );
     console.error(String((e as { stderr?: Buffer })?.stderr ?? e));
     process.exit(1);