artifact-store-tools: say what the artifact store holds and what the records name (hq ADR 0251) #123

Merged

mesh-admin merged 2 commits from feat/store-tools into main 2026-10-08 11:06:11 +00:00

Conversation 3 Commits 2 Files Changed 20

+1954 -220

2 Commits

Author	SHA1	Message	Date
jochen	24ce702360	Move the artifact store's tools into a module beside it, as the controller requires ... A module that provides the artifact store cannot build an artifact: building publishes to the store, so the store would be needed to create itself, and the module check refuses it. The tools become artifact-store-tools, assigned beside the store, and read manifests from the store's files through its container as they already read the listing, so they need no address for the store's door. Named for the artifact store, because "store" alone is the database server (hq glossary).	2026-10-08 12:04:33 +02:00
jochen	5f22ebbe97	distribution: say what the store holds and what the records name, so collection is no longer blind (hq ADR 0251) ... The store had no working tools: its TypeScript client was never built, and nothing could count what the store holds that no record names. A Go bundle lists the store's files through its own container, reads each manifest through its door, and sets that beside the controller's records. Collection is asked of the controller, which decides and records; the store's tools never delete. The image.pushed event was declared and never emitted, and nothing consumes it, so it goes.	2026-10-08 11:59:47 +02:00