The nightly distribution.collect (installed today 14:35, first run 2026-10-06 03:30) runs the stock registry garbage-collect, which keeps only blobs a manifest names. The mesh's bundles and archives are bare blobs no manifest names, so the first run would delete every one, current ones included (claude-code/tools, mesh-host/host-arch, mesh-controller/controller, node-tools/runtime and ~100 more). Measured read-only: 6 096 of 8 186 blobs unmarked; the current claude-code and mesh-host bundles are marked 0 times.
This adds --dry-run: the run reports what it would delete and deletes nothing. Real collection comes back once the controller holds each kept archive with a manifest (follow-up, hq issue 253). One-line change; module check ok.
The nightly `distribution.collect` (installed today 14:35, first run 2026-10-06 03:30) runs the stock `registry garbage-collect`, which keeps only blobs a manifest names. The mesh's bundles and archives are bare blobs no manifest names, so the first run would delete every one, current ones included (claude-code/tools, mesh-host/host-arch, mesh-controller/controller, node-tools/runtime and ~100 more). Measured read-only: 6 096 of 8 186 blobs unmarked; the current claude-code and mesh-host bundles are marked 0 times.
This adds `--dry-run`: the run reports what it would delete and deletes nothing. Real collection comes back once the controller holds each kept archive with a manifest (follow-up, hq issue 253). One-line change; `module check` ok.
The stock collector keeps only what a manifest names, and the mesh's bundles
and archives are bare blobs no manifest names: its first run, tonight at
03:30, would delete every one, the current ones included. It now reports
what it would delete and deletes nothing, until the controller holds each
kept archive with a manifest. hq issue 253.
Deliverynovox/mesh-catalog@ebacf79c91cd — held since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.
Delivery plan — builds distribution → novox; no bus step
tier 0: distribution
novox: receives distribution
distribution provides artifact-store: its consumers are sent again after it
distribution keeps data (ADR 0233): what it holds is backed up before it moves
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#62 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@ebacf79c91cd` — **held** since 2026-10-06T23:05:28Z
Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on.
**Delivery plan** — builds distribution → novox; no bus step
- tier 0: distribution
- novox: receives distribution
- distribution provides artifact-store: its consumers are sent again after it
- distribution keeps data (ADR 0233): what it holds is backed up before it moves
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#62 merged; its head was not heard by this owner, so it is made from the forge's word
- 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The nightly
distribution.collect(installed today 14:35, first run 2026-10-06 03:30) runs the stockregistry garbage-collect, which keeps only blobs a manifest names. The mesh's bundles and archives are bare blobs no manifest names, so the first run would delete every one, current ones included (claude-code/tools, mesh-host/host-arch, mesh-controller/controller, node-tools/runtime and ~100 more). Measured read-only: 6 096 of 8 186 blobs unmarked; the current claude-code and mesh-host bundles are marked 0 times.This adds
--dry-run: the run reports what it would delete and deletes nothing. Real collection comes back once the controller holds each kept archive with a manifest (follow-up, hq issue 253). One-line change;module checkok.Delivery
novox/mesh-catalog@ebacf79c91cd— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds distribution → novox; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.