v0.127.1

A target a monorepo releasable declares with a path resolves from the releasable's root for the one member owning it, so orxtra's top-level npm package syncs again; scaffold explains a releasable member missing its releasable-level merge bases.

Fixes

• Scaffolding a releasable member whose merge bases are not yet in its releasable's state directory explains why. A member scaffolded while its bases lived in its own .rlsbl/bases/ is refused once on its next scaffold; the refusal used to claim the member was scaffolded before merge-base tracking, and now says a member's bases live in .rlsbl-monorepo/releasables/<name>/bases/<member path>/ and it has none there yet. The remedy it names is unchanged: mkdir -p that directory and re-run rlsbl scaffold, which rebuilds each base from its last scaffold commit.
• A target a monorepo releasable declares with a path names one package again. A releasable config.json declaring {"name": "npm", "path": "npm"} handed that entry to every member, each resolving it against its own directory, so a releasable with a root member and library members looked for <member>/npm/package.json under every library and rlsbl monorepo sync refused the workspace. The path now resolves from the releasable's root (the deepest directory holding all its members), and only the member whose territory holds it carries the target; the missing-package.json refusal fires only when that one directory lacks one, and a path no member of the releasable contains is refused.