novox/mesh-catalog
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Manifests name their packages by full module path (issue 1966, bootstrap recovery) #631

Merged
mesh-tools merged 2 commits from fix/1966-packages-by-module-path into main 2026-11-08 00:01:30 +00:00
Conversation 1 Commits 2 Files Changed 28
+45 -43
2 Commits
Author SHA1 Message Date
jschoubben 1171b684d0 Round 1: distribution's manifest test expects the artifact-store alias the bootstrap keeps
mesh/delivery merged: source.main moved to novox/mesh-catalog@d03b455ea6e4
Details
mesh/check checking 1171b684d08b on d03b455ea6e4 
The review of 6547933b: the test still wanted the provision retired, though
80b8002a and 0c465fb9 keep it on port 5100 for the running node-engines; it
failed on main too (issue 1966).

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
 2026-11-08 01:00:40 +01:00
jschoubben 6547933b4d Name packages by their module path in 15 manifests (issue 1966) 
Kind: short package names (builds, sshkeys, forgemsg, backupgood,
diskreadings, grantsstate, busgrants) in `packages`, which the indexer's
judge refuses by design 32's rule (a Go package is named by its go.mod's
module path). This held mesh-delivery-gate, the build modules, mounts and
restic. Each key is now the import path the module's code uses, with its
series kept; the manifest tests read the new keys, and the host/machine-name
word tests in mounts, nfs-server, mesh-build-node and mesh-delivery-gate
look past the path's `git.novox.be/novox/` prefix.

Quick fix: only the gate's manifest. Thorough fix (chosen): all 15, since
the same refusal holds each. Follow-up for the checker: the candidate
verdict lets such a name through (J7(3)), so the merge check did not stop it.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
 2026-11-08 00:38:55 +01:00