rman 1.2.5 → 2.0.0-beta.2

package/core/manifest.js

@@ -1,4 +1,5 @@
 import path from 'node:path';
+import { RmanApplication } from './application.js';
 import { semverScheme } from './version-scheme.js';
 /**
  * The registry, merged onto the `Manifest` interface so one name carries both the shape and the
@@ -6,71 +7,53 @@ import { semverScheme } from './version-scheme.js';
  *
  * A namespace rather than loose `addManifestProvider`/`readManifest` functions because a namespace
  * is what a plugin can *augment*: `declare module 'rman' { namespace Manifest { ... } }` is how
- * `rman-node` already adds to `SystemInfo`, and anything this seam grows later can arrive the
+ * the `node` built-in already adds to `SystemInfo`, and anything this seam grows later can arrive the
  * same way instead of as another top-level export.
  */
 export var Manifest;
 (function (Manifest) {
-    /** Registers a provider. Called by `loadPlugins` for each plugin's `manifest`, in `plugins`
-     *  declaration order - so which one answers is a function of the repository's own config. */
-    function addProvider(provider) {
-        if (providers.includes(provider))
-            return;
-        providers.push(provider);
-    }
-    Manifest.addProvider = addProvider;
-    /** For tests, which would otherwise leak a provider into every later case in the process. */
-    function clearProviders() {
-        providers.length = 0;
-    }
-    Manifest.clearProviders = clearProviders;
     /**
-     * Reads `dir`'s manifest through the first provider that recognizes it, with the scheme that
-     * provider brings.
+     * Reads `dir`'s manifest through **the platform that already claimed it**, with the scheme that
+     * platform brings.
+     *
+     * **It takes a platform rather than searching for one**, and that is where the walk changed
+     * things. This used to loop over every registered platform, once per `Package` constructed - so a
+     * package asked "who am I?" and the answer was whoever recognized it first, re-derived at every
+     * construction. The walk decides it once per directory now (`Workspace.walk` ->
+     * `app.platformFor`) and hands it to the package, which is also what lets a nested Cargo package
+     * sit inside a Node monorepo: the platform is a fact about the directory, established by whoever
+     * found it, not re-guessed by whoever reads it.
      *
-     * **With no provider registered, or none recognizing the directory**, the fallback is a package
-     * named after its own directory at version `0.0.0`. That is deliberately the least it can claim:
-     * the directory name is a fact, and `0.0.0` is the version a thing has when nothing says
-     * otherwise. The alternative - refusing to construct a package at all - would make `rman info` and
-     * `rman list` fail in a repository whose `.rmanrc` simply names no plugin yet, which is exactly
-     * when someone needs to run them.
+     * **When that platform reads nothing** - `basePlatform`, or a provider that claimed the directory
+     * and then found nothing in it - the fallback is a package named after its own directory at
+     * version `0.0.0`. Deliberately the least it can claim: the directory name is a fact, and `0.0.0`
+     * is the version a thing has when nothing says otherwise. The alternative - refusing to construct
+     * a package at all - would make `rman info` and `rman list` fail in a repository whose `.rmanrc`
+     * simply names no plugin yet, which is exactly when someone needs to run them.
      */
-    function read(dir) {
-        for (const provider of providers) {
-            const manifest = provider.read(dir);
-            if (manifest) {
-                return {
-                    manifest,
-                    versionScheme: provider.versionScheme ?? semverScheme,
-                    fileName: provider.fileName,
-                    provider: provider.name,
-                };
-            }
-        }
+    function read(platform, dir) {
+        const provider = platform.manifestProvider;
+        const manifest = provider.read(dir);
         return {
-            manifest: { name: path.basename(dir), version: '0.0.0', raw: {} },
-            versionScheme: semverScheme,
-            /** Nothing was read, so nothing can be named - a caller listing "the file I changed" has no
-             *  file to list, which is correct rather than a placeholder that does not exist. */
-            fileName: '',
-            /** Same reasoning: no provider claimed this directory, so it belongs to no ecosystem. Empty
-             *  rather than a sentinel like `'unknown'`, which would read as an ecosystem's name and could
-             *  collide with a real provider's. */
-            provider: '',
+            manifest: manifest ?? { name: path.basename(dir), version: '0.0.0', raw: {} },
+            versionScheme: provider.versionScheme ?? semverScheme,
+            /** Nothing read means nothing to name - a caller listing "the file I changed" has no file to
+             *  list, which is correct rather than a placeholder that does not exist. */
+            fileName: manifest ? provider.fileName : '',
         };
     }
     Manifest.read = read;
     /** Writes through whichever provider recognizes `dir`. Throws when none does: a write that lands
      *  nowhere is worse than one that fails, since the caller has already decided the new version. */
-    function write(dir, manifest) {
-        for (const provider of providers) {
-            if (provider.read(dir)) {
-                provider.write(dir, manifest);
+    function write(app, dir, manifest) {
+        for (const platform of app.platforms) {
+            if (platform.manifestProvider.read(dir)) {
+                platform.manifestProvider.write(dir, manifest);
                 return;
             }
         }
         throw new Error(`No manifest provider recognizes "${dir}", so there is nowhere to write its version.\n` +
-            `  A repository's ".rmanrc" names its providers - see "plugins" (e.g. ['rman-node']).`);
+            `  A repository's ".rmanrc" names its technologies - see "plugins" (e.g. ['node']).`);
     }
     Manifest.write = write;
     /**
@@ -81,16 +64,16 @@ export var Manifest;
      * of can still describe its own graph by hand.
      */
     function dependenciesOf(pkg, candidates) {
-        return providerOf(pkg)?.dependencies?.(pkg.manifest, candidates) ?? [];
+        return platformOf(pkg)?.manifestProvider.dependencies?.(pkg.manifest, candidates) ?? [];
     }
     Manifest.dependenciesOf = dependenciesOf;
     /** `${{ pkg.scope }}`/`${{ pkg.unscopedName }}`, by whichever provider recognizes `dir` - and
      *  "no scope, the name is its own unscoped form" when none has an opinion. */
-    function splitName(dir, name) {
-        for (const provider of providers) {
-            if (!provider.read(dir))
+    function splitName(app, dir, name) {
+        for (const platform of app.platforms) {
+            if (!platform.manifestProvider.read(dir))
                 continue;
-            return provider.splitName?.(name) ?? { unscopedName: name };
+            return platform.manifestProvider.splitName?.(name) ?? { unscopedName: name };
         }
         return { unscopedName: name };
     }
@@ -102,19 +85,19 @@ export var Manifest;
      * reference each other by path has nothing here to go stale.
      */
     function updateDependencyVersions(pkg, bumped) {
-        providerOf(pkg)?.updateDependencyVersions?.(pkg.manifest, bumped);
+        platformOf(pkg)?.manifestProvider.updateDependencyVersions?.(pkg.manifest, bumped);
     }
     Manifest.updateDependencyVersions = updateDependencyVersions;
     /**
      * Rewrites a hard-coded version in `content` through `pkg`'s own ecosystem - see
-     * `ManifestProvider.stampVersion`.
+     * `Plugin.stampVersion`.
      *
      * `undefined` covers three cases the caller has to tell apart from each other, and cannot: no
      * provider claimed the package, the provider has no opinion about stamping, or it looked and found
      * nothing to change. All three mean "this file was not stamped", which is what `version` reports.
      */
     function stampVersion(pkg, file, content, version, options) {
-        return providerOf(pkg)?.stampVersion?.(file, content, version, options);
+        return platformOf(pkg)?.manifestProvider.stampVersion?.(file, content, version, options);
     }
     Manifest.stampVersion = stampVersion;
     /**
@@ -126,25 +109,24 @@ export var Manifest;
      * plugin: git tags then answer the boundary question alone.
      */
     async function publishedVersion(pkg) {
-        return providerOf(pkg)?.publishedVersion?.(pkg);
+        return platformOf(pkg)?.manifestProvider.publishedVersion?.(pkg);
     }
     Manifest.publishedVersion = publishedVersion;
-    /** The file names providers look for, for an error message that can say what was expected. */
-    function fileNames() {
-        return providers.map(p => p.fileName);
+    /** The file names the registered technologies look for, for an error message that can say what
+     *  was expected. */
+    function fileNames(app) {
+        return [...app.platforms].map(platform => platform.manifestProvider.fileName);
     }
     Manifest.fileNames = fileNames;
-    const providers = [];
     /**
-     * The provider that claimed `pkg`, found by the name it reported as `pkg.provider` - exact, and
-     * without re-reading the manifest off disk to work it out again.
+     * The technology that claimed `pkg`, or `undefined` when none did - with nothing to look up.
      *
-     * The probe is the fallback, not the rule: it covers a package constructed *before* its provider
-     * was registered, which `Repository.create` cannot produce (plugins load first) but a test
-     * arranging providers by hand can.
+     * This used to search a registry by `pkg.provider` and fall back to re-reading the directory,
+     * because a package could be constructed before the provider that would claim it was registered.
+     * It cannot now: a package is handed its `Platform` at construction, by the application that
+     * resolved it. The `name` test is what "none claimed it" looks like - see `basePlatform`.
      */
-    function providerOf(pkg) {
-        const byName = pkg.provider ? providers.find(p => p.name === pkg.provider) : undefined;
-        return byName ?? providers.find(p => p.read(pkg.dirname));
+    function platformOf(pkg) {
+        return pkg.platform.name ? pkg.platform : undefined;
     }
 })(Manifest || (Manifest = {}));

package/core/merge-config.d.ts

@@ -1,8 +1,19 @@
-/** The prefix that turns a key into an append instead of a replacement: `+before` adds to whatever
- *  `before` already resolved to, rather than taking its place. */
-export declare const APPEND_PREFIX = "+";
+/** Where a repository keeps command modules of its own, as a glob or a list of them. */
+export declare const COMMANDS_KEY = "commands";
 /**
- * Keys that **append whether or not you ask** - `+plugins` is accepted and means nothing extra.
+ * Keys that **append rather than replace**, which is the only append rman has.
+ *
+ * **There used to be a `+key` prefix on every key, and it is gone.** It said "add to what this
+ * resolved to below", which is exactly what `value` says - and `value` says it better: it composes
+ * (three layers each deriving from the one under them), it can reorder or filter rather than only
+ * append, and it does not need the merge to keep an append *outstanding* until the layer it belongs
+ * to turns up. The prefix also carried a bug `value` does not: appending onto a value that was a
+ * sole `${{ }}` expression returning an array nested it, because the merge promoted the expression
+ * *string* to a list and interpolation only later turned that element into the array (measured,
+ * `[['a','b'],'c']` where a literal list gave `['a','b','c']`).
+ *
+ * What is left is this list, where appending is not a choice the author makes per layer but what
+ * the key *means*.
  *
  * `plugins` is the whole list because it is the one key where replacing is never what anyone meant:
  * every other setting has a value a closer layer can sensibly overrule, while a plugin *adds
@@ -10,6 +21,12 @@ export declare const APPEND_PREFIX = "+";
  * brought. Replacing was the silent failure - `extends`-ing a toolchain config and then adding a
  * plugin of your own dropped the toolchain's, and what you noticed was `Unknown argument: publish`.
  *
+ * `commands` and `publishTargets` are the same kind of statement - what this repository has, in
+ * instances or in globs naming them - so they append for the same reason: a repository adding one
+ * of its own never means "and stop loading the ones my shared config brought". All three are what
+ * a config *contributes*, and a contribution list is exactly the case where replacing is never
+ * what anyone meant.
+ *
  * Do not extend this list casually: a key that always appends can never be *un*-said by a closer
  * layer, which is only acceptable where the value is a set of contributions rather than a decision.
  */
@@ -24,7 +41,7 @@ export declare const ALWAYS_APPEND: readonly string[];
  * carry one.
  *
  * A symbol is invisible to `Object.entries`, `JSON.stringify` and js-yaml, so the chain travels
- * through `mergeConfig`, `finalizeConfig` and `rman config` without any of them having to know it
+ * through `mergeConfig` and `rman config` without either of them having to know it
  * is there.
  *
  * Each entry is a link, not a single slot: three layers each deriving from the one below need
@@ -51,47 +68,29 @@ export interface PreviousValue {
 }
 /** Only these two can ask for `value`, so only these two are worth remembering a previous for. */
 export declare function carriesPreviousValue(value: unknown): boolean;
-/** `"+before"` -> `"before"`, or `undefined` for a key that isn't an append. */
-export declare function appendTarget(key: string): string | undefined;
 /**
  * Merges `source` onto `target` in place, the way every layer of rman config is combined - a
  * directory's own file forms, the directory chain, `"[selector]"` blocks, and an `extends` base.
  * One implementation for all of them, so they cannot disagree about what an append means.
  *
- * Plain keys replace, and nested objects merge recursively, as a deep merge always has. What this
- * adds is `+key`:
+ * Plain keys replace and nested objects merge recursively, as a deep merge always has. The two
+ * things it adds are the contribution keys, which append instead (`ALWAYS_APPEND`), and the record
+ * of what each key held underneath, so a closer layer can derive from it as `value`.
  *
  * ```yaml
- * # the root says          before: "rm ./build"
- * # a package adds        +before: "rm ./cache"
- * # it resolves to         before: ["rm ./build", "rm ./cache"]
+ * # the root says   before: "rm ./build"
+ * # a package says  before: "${{ [...value, 'rm ./cache'] }}"
+ * # it resolves to   before: ["rm ./build", "rm ./cache"]
  * ```
  *
- * Appending is the half a shared config can't live without: a base that declares
- * `before: ["rm ./build"]` otherwise forces every repository wanting one more step to restate the
- * whole list - which is a copy of the base, silently frozen at the version it was copied from.
- *
- * A scalar is promoted to a list on the way, so neither side has to be written as an array. With
- * nothing inherited, `+key` simply produces a one-element list.
+ * That is the half a shared config cannot live without: a base declaring `before: ["rm ./build"]`
+ * otherwise forces every repository wanting one more step to restate the whole list - which is a
+ * copy of the base, silently frozen at the version it was copied from.
  *
- * On a value that isn't a list, the prefix is **ignored** rather than an error, because there the
- * two spellings already mean the same thing: objects merge whether or not you asked them to, and a
- * scalar has nothing to append to, so `+key` behaves exactly as `key` would. Nothing is silently
- * dropped - the value still lands.
- *
- * `key` and `+key` in the same object are both honored, in that order: the replacement happens
- * first, then the append lands on top of it.
+ * **A `+key` prefix used to mean this and is refused now**, naming the key and what to write
+ * instead - see the check at the top of the loop.
  */
 export declare function mergeConfig(target: Record<string, any>, source: Record<string, any>, 
 /** The file `source` was read from, recorded per key - see `ORIGINS`. A caller merging a value it
  *  built rather than read (a selector block already carrying its own origins) passes nothing. */
 origin?: string): Record<string, any>;
-/**
- * Turns any `+key` still outstanding into its plain key, as a list - the "nothing was inherited"
- * case, where an append simply is the whole value.
- *
- * Called once on a fully resolved config, and only there: until then an outstanding append may
- * still find the layer it belongs to, and a config handed to a command must carry no `+key` at all
- * or every reader would have to know about them.
- */
-export declare function finalizeConfig<T>(config: T): T;

package/core/merge-config.js

@@ -1,8 +1,23 @@
-/** The prefix that turns a key into an append instead of a replacement: `+before` adds to whatever
- *  `before` already resolved to, rather than taking its place. */
-export const APPEND_PREFIX = '+';
+import path from 'node:path';
+/** Where a repository keeps command modules of its own, as a glob or a list of them. */
+export const COMMANDS_KEY = 'commands';
+/** The keys whose string entries are globs, and so have to be anchored to the file that wrote
+ *  them - see `anchorContributions`. The same three that always append. */
+const GLOB_KEYS = ['plugins', COMMANDS_KEY, 'publishTargets'];
 /**
- * Keys that **append whether or not you ask** - `+plugins` is accepted and means nothing extra.
+ * Keys that **append rather than replace**, which is the only append rman has.
+ *
+ * **There used to be a `+key` prefix on every key, and it is gone.** It said "add to what this
+ * resolved to below", which is exactly what `value` says - and `value` says it better: it composes
+ * (three layers each deriving from the one under them), it can reorder or filter rather than only
+ * append, and it does not need the merge to keep an append *outstanding* until the layer it belongs
+ * to turns up. The prefix also carried a bug `value` does not: appending onto a value that was a
+ * sole `${{ }}` expression returning an array nested it, because the merge promoted the expression
+ * *string* to a list and interpolation only later turned that element into the array (measured,
+ * `[['a','b'],'c']` where a literal list gave `['a','b','c']`).
+ *
+ * What is left is this list, where appending is not a choice the author makes per layer but what
+ * the key *means*.
  *
  * `plugins` is the whole list because it is the one key where replacing is never what anyone meant:
  * every other setting has a value a closer layer can sensibly overrule, while a plugin *adds
@@ -10,10 +25,16 @@ export const APPEND_PREFIX = '+';
  * brought. Replacing was the silent failure - `extends`-ing a toolchain config and then adding a
  * plugin of your own dropped the toolchain's, and what you noticed was `Unknown argument: publish`.
  *
+ * `commands` and `publishTargets` are the same kind of statement - what this repository has, in
+ * instances or in globs naming them - so they append for the same reason: a repository adding one
+ * of its own never means "and stop loading the ones my shared config brought". All three are what
+ * a config *contributes*, and a contribution list is exactly the case where replacing is never
+ * what anyone meant.
+ *
  * Do not extend this list casually: a key that always appends can never be *un*-said by a closer
  * layer, which is only acceptable where the value is a set of contributions rather than a decision.
  */
-export const ALWAYS_APPEND = ['plugins'];
+export const ALWAYS_APPEND = ['plugins', COMMANDS_KEY, 'publishTargets'];
 /**
  * Where a key keeps what it is replacing, so the replacement can be handed it back as `value`.
  *
@@ -24,7 +45,7 @@ export const ALWAYS_APPEND = ['plugins'];
  * carry one.
  *
  * A symbol is invisible to `Object.entries`, `JSON.stringify` and js-yaml, so the chain travels
- * through `mergeConfig`, `finalizeConfig` and `rman config` without any of them having to know it
+ * through `mergeConfig` and `rman config` without either of them having to know it
  * is there.
  *
  * Each entry is a link, not a single slot: three layers each deriving from the one below need
@@ -48,112 +69,61 @@ export const ORIGINS = Symbol('rman.origins');
 export function carriesPreviousValue(value) {
     return typeof value === 'function' || (typeof value === 'string' && value.includes('${{'));
 }
-/** `"+before"` -> `"before"`, or `undefined` for a key that isn't an append. */
-export function appendTarget(key) {
-    return key.length > APPEND_PREFIX.length && key.startsWith(APPEND_PREFIX)
-        ? key.slice(APPEND_PREFIX.length)
-        : undefined;
-}
 /**
  * Merges `source` onto `target` in place, the way every layer of rman config is combined - a
  * directory's own file forms, the directory chain, `"[selector]"` blocks, and an `extends` base.
  * One implementation for all of them, so they cannot disagree about what an append means.
  *
- * Plain keys replace, and nested objects merge recursively, as a deep merge always has. What this
- * adds is `+key`:
+ * Plain keys replace and nested objects merge recursively, as a deep merge always has. The two
+ * things it adds are the contribution keys, which append instead (`ALWAYS_APPEND`), and the record
+ * of what each key held underneath, so a closer layer can derive from it as `value`.
  *
  * ```yaml
- * # the root says          before: "rm ./build"
- * # a package adds        +before: "rm ./cache"
- * # it resolves to         before: ["rm ./build", "rm ./cache"]
+ * # the root says   before: "rm ./build"
+ * # a package says  before: "${{ [...value, 'rm ./cache'] }}"
+ * # it resolves to   before: ["rm ./build", "rm ./cache"]
  * ```
  *
- * Appending is the half a shared config can't live without: a base that declares
- * `before: ["rm ./build"]` otherwise forces every repository wanting one more step to restate the
- * whole list - which is a copy of the base, silently frozen at the version it was copied from.
- *
- * A scalar is promoted to a list on the way, so neither side has to be written as an array. With
- * nothing inherited, `+key` simply produces a one-element list.
+ * That is the half a shared config cannot live without: a base declaring `before: ["rm ./build"]`
+ * otherwise forces every repository wanting one more step to restate the whole list - which is a
+ * copy of the base, silently frozen at the version it was copied from.
  *
- * On a value that isn't a list, the prefix is **ignored** rather than an error, because there the
- * two spellings already mean the same thing: objects merge whether or not you asked them to, and a
- * scalar has nothing to append to, so `+key` behaves exactly as `key` would. Nothing is silently
- * dropped - the value still lands.
- *
- * `key` and `+key` in the same object are both honored, in that order: the replacement happens
- * first, then the append lands on top of it.
+ * **A `+key` prefix used to mean this and is refused now**, naming the key and what to write
+ * instead - see the check at the top of the loop.
  */
 export function mergeConfig(target, source, 
 /** The file `source` was read from, recorded per key - see `ORIGINS`. A caller merging a value it
  *  built rather than read (a selector block already carrying its own origins) passes nothing. */
 origin) {
-    // Plain keys first, so a `+key` alongside its own `key` appends to that replacement rather than
-    // to whatever the previous layer had.
     for (const [key, value] of Object.entries(source)) {
-        if (appendTarget(key))
-            continue;
-        /** `plugins`: additive at every layer, so the closer one adds rather than takes over. */
+        /**
+         * **A retired `+key` is refused, not ignored.** rman validates no config keys at all - there is
+         * no schema behind `.rmanrc`/`.rmanrc.yml` any more - so an unknown key is silent, and a
+         * repository upgrading from 1.x with `+before:` in its config would simply lose that step with
+         * nothing said. Measured before this check: `+include: ['extra']` resolved to the inherited
+         * list unchanged, exactly as if the line were not there.
+         *
+         * Here rather than in a validator, because this is the one function every layer passes through,
+         * and it is the only place that still knows which file the key came from.
+         */
+        if (key.length > 1 && key.startsWith('+')) {
+            const plain = key.slice(1);
+            throw new Error(`"${key}" is no longer a config key${origin ? ` (${origin})` : ''}. The \`+key\` prefix is ` +
+                `gone: write "${plain}" as a value that derives from what it inherited - ` +
+                `\`${plain}: ({ value }) => [...value, 'x']\`, or \`"\${{ [...value, 'x'] }}"\` in YAML. ` +
+                `\`value\` is the layers below this one, and spreads as empty when there are none.`);
+        }
+        /** `plugins`/`commands`/`publishTargets`: additive at every layer, so the closer one adds
+         *  rather than takes over. A glob among them is anchored to its own file on the way in - see
+         *  `anchorContributions`. */
         if (ALWAYS_APPEND.includes(key)) {
-            appendList(target, key, value);
+            appendList(target, key, GLOB_KEYS.includes(key) ? anchorContributions(value, origin) : value);
             continue;
         }
         assignMerged(target, key, value, source, origin);
     }
-    for (const [key, value] of Object.entries(source)) {
-        const plain = appendTarget(key);
-        if (!plain)
-            continue;
-        // An object merges either way, so the prefix asks for nothing extra - resolve it now and let
-        // the two spellings coincide.
-        if (isPlainObject(value) || isPlainObject(target[plain])) {
-            assignMerged(target, plain, value, source, origin);
-            continue;
-        }
-        if (plain in target) {
-            appendList(target, plain, value);
-            continue;
-        }
-        /** Nothing to append to *yet*. Kept as an append rather than collapsed into the plain key,
-         *  because the layer that provides it may still be coming: a directory's own file forms are
-         *  merged into an empty object long before the selector blocks and parent directories they
-         *  append to are. Collapsing here lost both of those - measured. `finalizeConfig` turns
-         *  whatever is still outstanding at the end into a plain list. */
-        target[key] = [...toList(target[key] ?? []), ...toList(value)];
-    }
     return target;
 }
-/**
- * Turns any `+key` still outstanding into its plain key, as a list - the "nothing was inherited"
- * case, where an append simply is the whole value.
- *
- * Called once on a fully resolved config, and only there: until then an outstanding append may
- * still find the layer it belongs to, and a config handed to a command must carry no `+key` at all
- * or every reader would have to know about them.
- */
-export function finalizeConfig(config) {
-    if (Array.isArray(config))
-        return config.map(finalizeConfig);
-    if (!isPlainObject(config))
-        return config;
-    const result = {};
-    for (const [key, value] of Object.entries(config)) {
-        const plain = appendTarget(key);
-        if (!plain) {
-            result[key] = finalizeConfig(value);
-            continue;
-        }
-        const pending = finalizeConfig(value);
-        result[plain] = plain in result ? [...toList(result[plain]), ...toList(pending)] : toList(pending);
-    }
-    /** Carried across by hand: this rebuilds the object from `Object.entries`, which does not see a
-     *  symbol - and dropping it here would lose every `value` chain the merge just recorded. */
-    for (const carried of [PREVIOUS_VALUES, ORIGINS]) {
-        const value = config[carried];
-        if (value)
-            Object.defineProperty(result, carried, { value });
-    }
-    return result;
-}
 function assignMerged(target, key, value, source, origin) {
     /** A source that already carries origins wins over the caller's: an `extends` base keeps the file
      *  its own keys were written in, rather than being attributed to the file that named it. */
@@ -178,25 +148,55 @@ function assignMerged(target, key, value, source, origin) {
      *
      * ```js
      * '[*]':    { clean: { include: ({ vars }) => [vars.buildDir] } }
-     * '[ws:*]': { clean: { include: "${{ [...value, pkg.basename + '.log'] }}" } }
+     * '[*]': { clean: { include: "${{ [...value, pkg.basename + '.log'] }}" } }
      * ```
      *
      * Chained here rather than at resolution time because only the merge knows the order of the
      * layers - by the time `interpolateConfig` sees the config they have collapsed into one object,
      * and whatever a closer layer said has already taken the place of what it was derived from.
      */
-    if (carriesPreviousValue(value) && key in target) {
+    /**
+     * **A chain already on `source` is carried over**, the way its `ORIGINS` are just above - and for
+     * the same reason: `source` may itself be several layers already merged, and only the merge knows
+     * their order.
+     *
+     * Without this, a chain recorded *inside* a source was silently dropped whenever the key was
+     * absent from the target, because the link below was only ever recorded for a key being
+     * *replaced*. The shape that hit it is the ordinary one for a shared config: a base and its
+     * consumer both writing `"[*]"`. Those two blocks merge into one before `matchingSelectors` sees
+     * them - recording the chain on the merged block - and that block is then merged into a `result`
+     * which has no such key, so the chain went nowhere.
+     *
+     * Measured, on a base declaring `clean.include: ['build']` and a consumer's `"[*]"` deriving from
+     * it: `${{ [...value, 'dist'] }}` answered `['dist']`, losing `build` outright. It answers
+     * `['build', 'dist']` now. Two *different* selectors (`"[*]"` then `"[pkg-a]"`) always worked,
+     * and so did an unmarked key, which is why this went unnoticed - those merge into a target that
+     * already holds the key.
+     */
+    const sourceChain = source[PREVIOUS_VALUES]?.[key];
+    if (carriesPreviousValue(value) && (key in target || sourceChain)) {
         const carrier = target;
         const chain = (carrier[PREVIOUS_VALUES] ??= {});
-        chain[key] = { value: target[key], previous: chain[key] };
+        /** The layer the target itself stands for, bottom-most of the three: what it holds now, over
+         *  whatever *that* was derived from. Absent when the target never had the key. */
+        const below = key in target ? { value: target[key], previous: chain[key] } : chain[key];
+        /** Bottom-up: the target's layer, then `source`'s own intermediate ones, then `value` on top -
+         *  so `source`'s chain keeps its internal order and gets the target's spliced beneath it. */
+        chain[key] = sourceChain ? graftChain(sourceChain, below) : below;
     }
     target[key] = Array.isArray(value) ? [...value] : value;
 }
+/** `node`'s chain, copied with `tail` spliced in beneath its deepest link - so two layer-stacks
+ *  join into one without either being mutated (a chain is shared by every package that resolved
+ *  through it, so grafting in place would rewrite what the others see). */
+function graftChain(node, tail) {
+    return { value: node.value, previous: node.previous ? graftChain(node.previous, tail) : tail };
+}
 /**
  * Appends `value` to `target[key]`, de-duplicating **only** an `ALWAYS_APPEND` key.
  *
  * That asymmetry is the point. `plugins` appends without being asked, so a repository and the config
- * it extends both naming `'rman-node'` is the ordinary case rather than a mistake, and the list is
+ * it extends both naming `'node'` is the ordinary case rather than a mistake, and the list is
  * also what `rman config` prints. An explicit `+before`, by contrast, was *written* - repeating a
  * step that is already there is a strange thing to ask for, but it is what was asked for, and
  * silently collapsing it would make one layer's list depend on another's contents.
@@ -212,6 +212,51 @@ function appendList(target, key, value) {
 function toList(value) {
     return Array.isArray(value) ? value : [value];
 }
+/**
+ * Anchors every glob in `plugins`/`commands`/`publishTargets` to the directory of the file that
+ * declared it, on the way in. A non-string entry - an instance written straight into the config -
+ * passes through untouched.
+ *
+ * **Done here, at the merge, because this is the last moment the answer is known.** `commands`
+ * always appends, so one resolved list ends up holding entries from the repository's own
+ * `.rmanrc`, from each `extends` base, and from every directory above - and `ORIGINS` records one
+ * file per *key*, not per element, so after the merge there is nothing left to attribute them by.
+ * Rewriting each glob as it arrives makes the merge trivially correct and costs one `path.resolve`.
+ *
+ * It is what lets a **shared config ship its own contributions**: `commands: './commands/*.js'`
+ * in a published package means that package's directory, wherever the repository inheriting it
+ * happens to sit. All three keys behave the same way; `plugins` used to resolve every entry
+ * against the repository root instead, whatever file declared it, and that asymmetry is gone.
+ *
+ * `origin` is absent when a caller merges a value it built rather than read (a selector block, the
+ * directory chain layering already-resolved configs); those globs have been anchored already, and
+ * an absolute path is left alone by `path.resolve` anyway.
+ */
+function anchorContributions(value, origin) {
+    if (!origin)
+        return value;
+    const dir = path.dirname(origin);
+    const anchor = (entry) => typeof entry === 'string' && !looksLikePackageName(entry) ? path.resolve(dir, entry) : entry;
+    return Array.isArray(value) ? value.map(anchor) : anchor(value);
+}
+/**
+ * Whether an entry is shaped like a **package name** rather than a glob - `rman-node`,
+ * `@panates/rman-node`, but not `*.js`, `./x.js` or `commands/*.mjs`.
+ *
+ * Such an entry is left unanchored, because it is not a relative path and turning it into one
+ * destroys the only evidence of what the author meant. A package name is never valid in these keys
+ * (a package's config arrives through `extends`), so the whole value of keeping it intact is the
+ * error message: anchored, `plugins: ['rman-node']` failed with `glob ".../rman-node" matched no
+ * file`, which sends the reader to check their paths. `loadPlugins` can now say what they actually
+ * wrote and what to write instead - which two doc pages already promised it did.
+ *
+ * Shape, not a resolver call: decidable without touching the disk, and a wrong guess only chooses
+ * which of two error messages a failing entry gets. An extension is excluded so a bare `plugin.js`
+ * beside the config is still anchored as the relative path it is.
+ */
+function looksLikePackageName(entry) {
+    return /^(?:@[a-z0-9-~][\w.-]*\/)?[a-z0-9-~][\w.-]*$/i.test(entry) && !/\.[cm]?js$/i.test(entry);
+}
 /** A config object, as opposed to an array or anything with its own prototype - only the former
  *  merges key by key. */
 function isPlainObject(value) {