The development loop (commons 0001-librariesFR-011, FR-012): the libraries a working tree changes, and the libraries that depend on them, type-checked and tested in parallel processes and no more than they need, with a calm summary. It is what a person or an agent runs between two edits; the release loop (the packing of every library, the register, the versions) is another command and is never part of this one.
bun run dev:check the libraries affected since origin/main (and the files not yet committed), their types and their tests bun run dev:check --only system,net those libraries and their dependents, whatever changed bun run dev:check --files a.ts,b/c.ts the libraries these files affect (paths from the repository's root) bun run dev:check --all every library bun run dev:check --list say what is affected and run nothing other flags: --base REF (origin/main by default), --no-types, --no-tests, --no-license, --bail (stop at the first failing test), --repo DIR
Nothing is installed per library. The repository's root installs the packages every library shares (bun install, once), the libraries are linked under commons/node_modules (a link for each folder whose package name is @intellectual-frontiers/<folder>), so that a library that imports another by its package name reads the checkout's source, never a copy from a registry: the exports of each package are the sources. A library with a package of its own outside the shared set (a database driver) is installed in its folder, once. The affected libraries are those of affected.ts (the same code the workflow of CI runs); TypeScript 7 checks each library's own tsconfig.json, several at a time, and the tests of each run in a bun test process of its own, from its folder as verify runs them, several at a time.
Links the libraries under commons/node_modules where they are not linked yet (link.ts, which bun run dev:check runs before this command can import any of them).
The license of the repository and of each library, as the check of license.ts finds it: a library with no LICENSE fails here, and the sentence says the command that writes it.
The tests of the libraries: one bun test suite/ process for each library, from its folder as its verify runs it, several at a time and the largest suites first. One process for all of them would be fewer, but a test may set what is global to its process (the tracer of a process, a working folder), and what it sets must not reach the tests of another library.