FR-001 | check | bun test suite/ | libraries.test.ts: the manifest is read as data and never run, an unknown field and a second export are refused, and the check names where the manifest and its folder disagree |
FR-002 | check | bun test suite/ | libraries.test.ts: the section of the libraries and the rows of enforcement.tsv are what the manifests make, and --check names the file that is not |
FR-003 | check | bun test suite/ | affected.test.ts: the libraries a change affects by folder and by dependency, the inputs of a library, and the matrix a workflow reads |
FR-004 | check | bun test suite/ | workflows.test.ts: the typed model, its validation findings and the rendering of the YAML, the same bytes for the same values |
FR-005 | check | bun test suite/ | workflows.test.ts: the generator makes the files, finds a hand-written workflow and a missing packer, and the publish workflow tags a version that is already on the registry |
FR-006 | check | bun test suite/ | pins.test.ts: the pins of an env file and the release asset of each platform; the installer is run by the workflows of this repository |
FR-007 | check | bun run verify | the package is built, inspected and packed by tools/pack.ts; tests/release/commons-packages.test.ts packs every library of npm, refuses one with no declaration for an export and type-checks a consumer |
FR-008 | check | bun test suite/ | mizan.test.ts, mizan-levels.test.ts, mizan-changes-git.test.ts and versions-git.test.ts, and in libraries mizan-oscal-register.test.ts and mizan-newer.test.ts: each command run on real folders and repositories |
FR-009 | check | bun test suite/ | mizan-nist-import.test.ts: the committed module names the controls the specifications cite with the titles of the pinned catalog, and the offline check passes |
FR-010 | check | bun run verify | the package is built, inspected and packed by tools/pack.ts; the commands run as bun commons/libraries/src/<command>.ts in the workflows of this repository |
FR-011 | check | bun test suite/ | dev.test.ts: the counts and failures read from bun test, the packages a library installs itself, the libraries linked by name, what each scope affects, the summary, and a real run with a type error and a failing test |
FR-012 | check | bun test suite/ | plan.test.ts: the cells on Linux and on the systems a library's record names, the outputs of a step, the command on this repository, and the one workflow ci |
FR-013 | check | bun test suite/ | releasing.test.ts: each rule of the plan on facts, a breaking impact raising the minor while the major version is 0, and on a real repository with tags and commits |
FR-014 | check | bun test suite/ | releasing.test.ts: apply refreshes the lockfiles, makes the generated files once, synchronizes, runs the proof last and writes the record, and publishes and tags nothing; release-lockfile.test.ts: on a real repository with a stale lockfile the gate passes after apply and fails without the refresh; matrix leaves out what is tagged |
FR-015 | check | bun test suite/ | workflows.test.ts: the release workflow is by hand from main, in the order of the record, with provenance and the token only where there is one |
FR-016 | check | bun test suite/ | family.test.ts: the family field is decoded, the reserved names are found as data with no folder, and each side of a family held against the host's table is found |
FR-017 | check | bun test suite/ | readme.test.ts: the summary and the first clause are read as data, a row is made from each manifest, the table is sorted by role and name, a library with no role is a problem, --check writes nothing and fails where the README is stale, and the real README is what the manifests make |
FR-018 | check | bun test suite/ | readme.test.ts: the real README has none of the words of history and every link to a path of the repository names a file or folder that exists |
FR-019 | check | bun test suite/ | license.test.ts: --check writes nothing and names a missing or a hand-edited LICENSE, a changed official text is refused, the packer writes the SPDX id and packs the LICENSE |
FR-020 | check | bun test suite/ | releasing.test.ts: the version is written into each constant the manifest names, and a missing file or constant is a sentence |
FR-021 | check | bun test suite/ | libraries.test.ts: two libraries that hold one number are given one each, the first in the section keeping it |
FR-022 | check | bun test suite/ | metapackages.test.ts: publishes and bundle are read, and the three refusals; releasing.test.ts: the release uses the package a manifest publishes |
FR-023 | check | bun test suite/ | metapackages.test.ts: the members, the exact dependencies, the generator and its --check, the packer and the order in the plan |
FR-024 | check | bun test suite/ | held.test.ts: the closed kinds, the refusals of the decoder, the distribution and the sets, the README row; metapackages.test.ts: a held library is not in the facts of a release |
FR-025 | check | bun test suite/ | libraries.test.ts: a spec kit that docs.config.ts does not list is a finding naming the library and the line, a listed one is none; repoctl library-commit-doctor.test.ts: new library lists its spec kit |
FR-026 | check | bun test suite/ | held.test.ts: the plan names each library that is not released with its kind and sentence, --raise of one is refused with its reason, and on a real repository the held library is out of the steps |
FR-027 | check | bun test suite/ | release-floor.test.ts: the floor of removed and added keys, the greater of it and the commits wins, 0.x and 1.x, the reason in the plan, and on a real repository against a registry simulator that serves the manifest of a version |
FR-028 | check | bun test suite/ | pack-commons.test.ts: the mode is one of two, the repository is in single mode, the environment names the other for one run and a value that is no mode is refused; tests/release/commons-packages.test.ts: the per-library machinery works again under IFC_DISTRIBUTION=per-library |
FR-029 | check | bun test suite/ | pack-commons.test.ts: the exports of each library, the rewriting of specifiers, the union of dependencies, the commands, the files that do something when loaded, the runtime folders and the packer on the real files of a small repository; tests/release/commons-package.test.ts packs the real libraries |
FR-030 | check | bun test tests/release/commons-package.test.ts | the one package is packed from the real libraries, inspected, installed with npm and with Bun, every entry imported on Node 26 and Bun, its commands run and a consumer type-checked with and without dom; pack-commons.test.ts shows each check that matters on a copy made to fail |
FR-031 | check | bun test suite/ | pack-commons.test.ts: the tools of the package are derived from the manifests and the sources, a package the libraries need that the folder lacks is a finding, and the real folder is what the derivation makes; tests/release/commons-ci.test.ts: a fresh clone with only the folder installed packs the package |
FR-032 | check | bun test suite/ | release-single.test.ts: single mode plans one release raised by the greatest Impact across the libraries, a held library counted, and the registries are github alone, the publication sending the tarball to the GitHub package registry and tagging |