31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
---
|
|
status: located
|
|
opened: 2026-10-03
|
|
located-in:
|
|
- mesh-controller
|
|
fixed-by:
|
|
amended-design:
|
|
---
|
|
|
|
# 216 — A tools bundle nothing says to load is built, recorded, and never delivered
|
|
|
|
## What was observed
|
|
|
|
2026-10-03, seven modules moved their tools from a container to a bundle. Each built, each build was
|
|
recorded, and the machines that run them reported current — with none of the bundles on them. The
|
|
composer delivers a bundle only when the runtime loads something from it, and that is derived from
|
|
the module's `tools` list when the artifact names no `loads`; these modules had neither.
|
|
|
|
## Why it matters beyond this instance
|
|
|
|
Every step reported success: the build, the registration, the push, the machine's apply. The tools
|
|
were simply absent, and the old container was gone. A rule the composer applies silently is a rule
|
|
nobody learns until the tools are missing.
|
|
|
|
## Diagnosis
|
|
|
|
Owner mesh-controller (the catalogue's registration check). **Fix direction:** a bundle that nothing
|
|
loads, runs or unpacks — no `loads`, no `tools` list on its module, no resource naming it — is refused
|
|
at registration, naming the field that would deliver it. A test: such a manifest is refused; adding
|
|
`loads` admits it.
|