Write showcase's tools and provisioner against the SDK's registerModuleTools and runProvisioner, so it type-checks (issue 894)

modules/showcase/provisioner/index.ts

@@ -1,20 +1,19 @@
 // showcase's provisioner — how a consumer is given an instance of what this module provides.
 //
 // **A provider ships the provisioner that creates instances of the resource it offers** (ADR
-// 0040). The mesh asks; this adapts that request to whatever the software actually needs, and
-// hands back what the consumer is given.
-import { provisioner } from "@novox/mesh-sdk/provisioner";
+// 0040). The mesh asks; this adapts that request to whatever the software actually needs. The
+// reconcile loop is the sdk's (`runProvisioner`); this writes only the per-service half.
+import { runProvisioner, type Provision } from "@novox/mesh-sdk/provisioner";
 
-await provisioner({
-  provision: "greeting",
-  async create({ consumer }: { consumer: string }) {
+runProvisioner("greeting", {
+  async create(p: Provision): Promise<void> {
     // A real provider would create something here — a database, a vhost, an account. This one has
-    // nothing to create, so it returns what a consumer is told, which is the half that matters:
-    // the mesh seals it and delivers it, and the consumer never sees this code.
-    return { serves: { greeting: `hello ${consumer}` } };
+    // nothing to create: what a consumer is told is the manifest's `serves` block, which the mesh
+    // fills for this consumer, seals and delivers (ADR 0048), so the consumer never sees this code.
+    console.log(`[showcase] greeting ready for ${p.consumer ?? p.as}`);
   },
-  async remove() {
+  async remove(): Promise<void> {
     // Removal is not optional. A provider that cannot take an instance back leaves the mesh unable
-    // to unassign a consumer without leaking whatever it was given.
+    // to unassign a consumer without leaking whatever it was given. Nothing was made, so nothing goes.
   },
 });