chore: les paquets ng-org rattrapent le deploiement, et la lecture vive demarre

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

@@ -261,9 +261,11 @@ async function main(): Promise<void> {
     }
     check(CHECKS[4]!, remaining === 0, `triples left for the seeded subject: ${remaining}`);
 
-    // Only worth asking when the five-argument call did NOT start: it is the diagnosis of
+    // Only worth asking when the published call did NOT start: it is the diagnosis of
     // that failure, and a deployment that answers the published arity has nothing to
-    // characterise.
+    // characterise. Since `@ng-org/web@0.1.2-alpha.14` the published call is itself the
+    // six-argument one, so this asks whether the engine refuses a start the client got
+    // right - no longer whether the client was sending the wrong number.
     if (readyMs === null) {
       const withConfig = await sdk<{ doc: string; error: string | null }>(
         frame,
@@ -273,12 +275,12 @@ async function main(): Promise<void> {
         CHECKS[5]!,
         withConfig.error === null
           ? "six arguments with `{}` in position 4 are ACCEPTED — the deployed " +
-              "`orm_start_graph` takes a `config` BEFORE the callback, so the published " +
-              "client's five-argument call puts its callback there"
+              "`orm_start_graph` takes a `config` BEFORE the callback, which is what the " +
+              "published client now sends, so the refusal is not an arity mismatch"
           : `six arguments were refused too: ${withConfig.error}`,
       );
     } else {
-      record(CHECKS[5]!, "not asked — the published five-argument call started");
+      record(CHECKS[5]!, "not asked — the published six-argument call started");
     }
   } finally {
     if (page) await closeQuietly("the ORM live-read page", () => page!.close());