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

e2e/bridge.ts

@@ -14,7 +14,7 @@
  * ends up typed as a reference.
  */
 
-import type { CurationReport, IndexEntry, UnionSubject } from "../src/index";
+import type { IndexEntry, UnionSubject } from "../src/index";
 
 /** What the leak probe observed — see `run.ts`'s last journey. */
 export interface BrokenInboxOutcome {
@@ -60,8 +60,15 @@ export interface IndexingBridge {
   referConfigured(object: string): Promise<void>;
   /** Hand a NAMED index a reference — used where no identity boundary is crossed. */
   referTo(index: string, object: string): Promise<void>;
-  /** Resolve the references this index received and add what can be added. Owner only. */
-  curate(index: string): Promise<CurationReport>;
+  /**
+   * Connect again — obtain a fresh `Indexing` handle, which is what a page load does.
+   *
+   * There is no curating act to drive: an index is curated at its creator's next
+   * connection and on each deposit while the creator is connected. This is the first
+   * of the two, driven deliberately so a journey has a point at which the catching
+   * up is over; the second needs nothing from anyone.
+   */
+  reconnect(): Promise<void>;
   /** The index's entries, ordered by value. */
   read(index: string): Promise<IndexEntry[]>;