A resolved manifest keeps a built reference in the store's own form, never the address it was reached by (hq ADR 0155) #230

2026-10-02T21:13:53Z

mesh-admin commented

2026-10-02 21:13:53 +00:00

Found live, 2026-10-02 21:08. The first bundle resolved on the mesh (node-tools, to-be 38 WP3) was built, heard and recorded, and not registered: bundles[0].source carried the artifact store's host, and the rule that a definition names no installation (ADR 0155) refused it, correctly.

The build record already keeps references in the store-relative artifact-store:// form (Recorded). The resolved manifest now does the same for a bundle's source and for an archive resource's source; composition routes a kept reference through the store a machine reaches (Routed), as it already did. Test: a bundle and an archive resolved from http://<store>/v2/…/blobs/… keep the store form and the resolved manifest names no installation.

Needed before node-tools can register; rebuilding node-tools after this rolls registers it (the build record is idempotent).

**Found live, 2026-10-02 21:08.** The first bundle resolved on the mesh (node-tools, to-be 38 WP3) was built, heard and recorded, and **not registered**: `bundles[0].source` carried the artifact store's host, and the rule that a definition names no installation (ADR 0155) refused it, correctly. The build record already keeps references in the store-relative `artifact-store://` form (`Recorded`). The resolved manifest now does the same for a bundle's `source` and for an archive resource's `source`; composition routes a kept reference through the store a machine reaches (`Routed`), as it already did. Test: a bundle and an archive resolved from `http://<store>/v2/…/blobs/…` keep the store form and the resolved manifest names no installation. Needed before node-tools can register; rebuilding node-tools after this rolls registers it (the build record is idempotent).

mesh-admin added 1 commit 2026-10-02 21:13:53 +00:00

A resolved manifest keeps a built reference in the store's own form, never the address it was reached by (hq ADR 0155) 28c7f05b39

The first bundle resolved on the mesh carried the store's host in bundles[0].source, and registration
refused node-tools as naming an installation — rightly. The build record already keeps the
store-relative form; the resolved manifest now keeps the same for bundles and archive resources,
and composition routes it through the store a machine reaches, as it already did for a kept one.

mesh-admin merged commit 11a44e1ec4 into main

2026-10-02 21:14:06 +00:00

mesh-admin deleted branch fix/a-resolved-reference-is-kept-not-routed

2026-10-02 21:14:06 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#230