@celilo/cli 1.9.1 → 1.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celilo/cli",
-  "version": "1.9.1",
+  "version": "1.10.0",
   "description": "Celilo — home lab orchestration CLI",
   "type": "module",
   "bin": {

package/src/manifest/contracts/v1.ts

@@ -311,6 +311,30 @@ export const V1_HOOKS: ContractHooks = {
     inputs: {},
     outputs: {},
   },
+  /**
+   * Reclaim disk a module's own store has accumulated and has no way to
+   * release on its own.
+   *
+   * Distinct from `on_backup`'s retention, which prunes copies celilo itself
+   * made and records. This is for state the module's SERVICE owns and celilo
+   * never sees — a registry's package store, a cache, an artifact directory —
+   * where the only thing that knows what is superseded is the service.
+   *
+   * Deliberately not a converge hook: convergence re-asserts a desired state
+   * and is safe to run constantly, while this DELETES and its mistakes are not
+   * recoverable. So it declares its retention policy in config, supports a dry
+   * run, and is expected to be conservative — the celilo-registry sweep never
+   * removes the last revision of a release, which is what makes running it
+   * unattended defensible.
+   *
+   * Driven on demand (`celilo module run-hook <module> sweep_revisions`) and,
+   * where the store grows without an operator, by a `timer.tick.*`
+   * subscription.
+   */
+  sweep_revisions: {
+    inputs: {},
+    outputs: {},
+  },
   /**
    * Build-bus upstream publish hook. The executor passes the
    * PublishEvent fields as env vars (CELILO_EVENT_PAYLOAD,

package/src/manifest/schema.ts

@@ -366,6 +366,7 @@ const LIFECYCLE_HOOK_SCHEMAS = {
   reconcile_clients: LifecycleHookSchema.optional(),
   list_peers: LifecycleHookSchema.optional(),
   reconcile_peers: LifecycleHookSchema.optional(),
+  sweep_revisions: LifecycleHookSchema.optional(),
 } satisfies Record<HookName, z.ZodTypeAny>;
 
 /**