Join (lead's i): the builder follows the indexer's packages and numbers a package once its name is known

The indexer's packages state is read through its read tool's first view and its views family (ADR 0615 §1), as the
other four states the builder follows, not by its bucket: the manifest drops the read, invokes indexer_read_packages and
consumes views.packages.

A package built unnumbered because its name was not known at its claim was numbered only at its module's next claim.
Now a series key heard naming a name looks at its module again (Builder.PackageNamed), and a look at a done trunk build
numbers what it left unnumbered with the done key's digests (BuildClaim.Done), so version.numbered carries the digest
for the build module's late publish. Woken by the views family, never a timer.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

modules/mesh-delivery-builder/module.json

@@ -50,7 +50,8 @@
     "mesh-delivery-assigner.views.placement",
     "mesh-delivery-indexer.views.candidates",
     "mesh-delivery-indexer.views.manifests",
-    "mesh-delivery-indexer.views.modules"
+    "mesh-delivery-indexer.views.modules",
+    "mesh-delivery-indexer.views.packages"
   ],
   "invokes": [
     "mesh-delivery-forge-bridge.bridge_tags",
@@ -69,7 +70,8 @@
     "mesh-delivery-assigner.assigner_read_placement",
     "mesh-delivery-indexer.indexer_read_candidates",
     "mesh-delivery-indexer.indexer_read_manifests",
-    "mesh-delivery-indexer.indexer_read_modules"
+    "mesh-delivery-indexer.indexer_read_modules",
+    "mesh-delivery-indexer.indexer_read_packages"
   ],
   "state": [
     { "name": "builds", "history": 5 },
@@ -95,8 +97,7 @@
     "mesh-build-image.steps",
     "mesh-build-node.steps",
     "mesh-build-node.toolchains",
-    "mesh-delivery-gate.source",
-    "mesh-delivery-indexer.packages"
+    "mesh-delivery-gate.source"
   ],
   "uses": [
     "node-build-go",