artifact-store-tools: require no artifact-store; the sweep reaches the store through the registry seats (issue 1966)

The operator's decision of 2026-11-04: the store's clean-up asks the registry seats' verbs and is no consumer of the
provision.

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

modules/artifact-store-tools/README.md

@@ -6,12 +6,12 @@ directory and the file the mesh writes there from its setting `older-store-names
 
 ## Why a module beside the store
 
-The store is the `distribution` module. A module that provides the artifact store cannot also build an
-artifact: building publishes to the store, so the store would be needed to create itself, and the
-controller's module check refuses that manifest. So the store's tools are a second module, as the
-controller's refusal says to do. **Assign it to the machine that holds the store**: its tools read the
-store's files through the store's own container, and anywhere else they answer that the container is not
-on that machine.
+The store is the `distribution` module, the registry seats' holder. These tools became a module of their own when the
+indexer's judge refused a store holder that builds an artifact; that rule is gone (issue 1966), and the sweep stays its
+own module, holding the seat `mesh-artifact-sweep`. It requires no provision: what it holds, releases and removes it
+asks the registry seats `oci-artifact-registry` and `container-image-registry` (see *The sweep through the registry
+seats*). **Assign it to the machine that holds the store**: its read tools read the store's files through the store's
+own container, and anywhere else they answer that the container is not on that machine.
 
 ## Tools