The latest release is placed whatever the range a package.json names
(ADR 0573 §2); one outside that range is now said in the journal, for
the SDK and every other mesh package, so a module built against a
release its range excludes is visible. A range of a form not read is
said as such.
Builds: design 47 H H-A-267, H-A-276
A fetch naming a member's build of a mesh package the registry lacks
lays the build and waits on nothing; without the skip in
placeMeshPackages it waits for the registry's release.
Builds: design 47 H H-A-267
The keeper never marks a first view listing no module as answered
(A-367), so the subtest waited for what cannot come and hid every later
subtest. It waits for the first fill pass and takes it as the first.
Builds: design 47 H H-A-268
A trunk build put only the SDK into a module's node_modules; any other
@novox/mesh-* package its package.json names was left out of the install
and only a group or a member's build brought it, so the forge module's
build failed with "Cannot find module" for its contracts package. Each
such package is now placed at the latest release the registry holds, as
the SDK is; a group's packed package or a member's build still takes
precedence.
Builds: design 47 H H-A-267