feat!: curer n'est plus un appel, c'est ce que fait le traitement de l'inbox

test/public-surface.test.ts

@@ -9,7 +9,6 @@ import {
   polyfillPort,
   ENTRY_VALUE,
   INDEX_FIELD,
-  type CurationReport,
   type IndexEntry,
   type NextGraphPort,
 } from "../src/index";
@@ -22,21 +21,28 @@ test("the published surface carries the whole loop, end to end", async () => {
   const ownerPort: NextGraphPort = network.portFor("alice");
   const strangerPort: NextGraphPort = network.portFor("bob");
 
-  const owner = indexing(ownerPort);
-  const stranger = indexing(strangerPort);
+  const owner = await indexing(ownerPort);
+  const stranger = await indexing(strangerPort);
 
   const index = await owner.createIndex(PUBLISHED_AT);
   const article = await publishObject(strangerPort, PUBLISHED_AT, "2026-07-08");
   await stranger.refer(index, article);
 
-  const report: CurationReport = await owner.curate(index);
-  expect(report.index).toBe(index);
-  expect(report.outcomes).toEqual([{ result: "indexed", object: article, value: "2026-07-08" }]);
+  // NOBODY CURATES — there is nothing on this surface to call. Alice is connected,
+  // so her session is told a deposit landed and processes that inbox itself.
+  await network.deliverNotifications();
 
   const entries: IndexEntry[] = await owner.read(index);
   expect(entries).toEqual([{ object: article, value: "2026-07-08" }]);
 });
 
+test("the published surface offers no way to run, aim or schedule curation", async () => {
+  const handle = await indexing(new FakeNextGraph().portFor("alice"));
+  // Read off the handle rather than from a list: an application gets these three
+  // acts and nothing else, and curation is not one of them.
+  expect(Object.keys(handle).sort()).toEqual(["createIndex", "read", "refer"]);
+});
+
 test("the published surface exposes the deposit decoder and the two IRIs it writes", () => {
   expect(decodeReference("did:ng:o:doc-1")).toBe("did:ng:o:doc-1");
   expect(decodeReference({ object: "did:ng:o:doc-1" })).toBeNull();