/**
 * Published-package `./package.json` subpath lock (mmnto-ai/totem#2917).
 *
 * Every public workspace package exposes its own manifest through its exports
 * map, so `require('@mmnto/<pkg>/package.json')` and
 * `import.meta.resolve('@mmnto/<pkg>/package.json')` resolve instead of
 * throwing ERR_PACKAGE_PATH_NOT_EXPORTED. Two consumers measured the throw
 * on 2.9.1 before this lock existed (strategy's leg charters, and every
 * cohort pin-sync's installed-version check) and fell back to reading the
 * file by path.
 *
 * The lock reads the WORKSPACE manifests, not a packed tarball, and proves
 * the subpath two ways: the map carries the self-referential key, and Node's
 * own resolver reaches the manifest through that map. The second half uses
 * package self-referencing (a package may import itself by name when it
 * declares `exports`), which is a real exports-map resolution against the
 * source manifest with no install step. Private workspace packages are not
 * published and are out of scope.
 */
export {};
//# sourceMappingURL=published-exports-lock.test.d.ts.map