The generator and the packer of the metapackages (commons 0036-distributionFR-007, FR-008): the file of each set that records its exact dependencies, and the tarball of its package.
bun commons/libraries/src/pack-metapackage.ts write the file dependencies.auto.json of every metapackage again from the manifests bun commons/libraries/src/pack-metapackage.ts --check write nothing and exit 1 where a file is not what the manifests make bun tools/pack.ts [--check] (in the folder of a metapackage) stage, inspect and pack its package other flags: --repo DIR (the repository, the working folder by default)
A metapackage is a folder commons/<set>/ whose manifest names bundle; the folder holds the manifest, a private package.json, the LICENSE and tools/pack.ts, and nothing that is code. Its members come from the manifests (membersOf) and are written to dependencies.auto.json in its folder, so that a change of the set is a change of the folder, which the release sees. The packer writes the staged package (package.json with the exact dependencies, an empty index.js and its declaration, the README, the LICENSE), inspects it with the same inspection as every library's and packs it with bun pm pack.