@mnci/cli 4.44.0 → 4.46.0

package/README.md

@@ -514,6 +514,9 @@ packages under mnci (the plan is #383). So far it is **report mode only and chan
 mnci adopt          # what was found, what blocks, what clears each
 mnci adopt --json   # the same, as one document
 mnci adopt --tags   # step (#379): create the baseline release tags, locally
+mnci adopt --toolchain [--nx <version>]   # step (#380): retire old tooling, align Nx, pass the audit
+mnci adopt --overlay --scope @org --registry npm --agent ubuntu-latest   # step (#381): the overlay and pipeline
+mnci adopt --kinds [--kind apps/api=node-app]   # step (#378): record each project's kind
 ```
 
 It reads git and the filesystem (no Nx, no install, no network) and reports the package manager, the
@@ -529,6 +532,34 @@ disk version. `mnci adopt --tags` creates, for each such project, a lightweight
 commit of the old one (`@auto/mysql@1.12.11` on `mysql@1.12.11`). It is local and idempotent, never moves a tag,
 and prints the `git push` for you to run: publishing tags changes the remote, so that stays your decision.
 
+**`--toolchain`** brings the root toolchain to what mnci supports, as one diff to review. It refuses a directory
+that is not a clean git work tree and leaves its changes uncommitted, as `mnci upgrade` does. It removes the
+retired formatter configs and dependencies (Prettier, oxfmt, oxlint), the root scripts that call them (a
+`format:check` running `oxfmt` fails once the dependency is gone), and the local-registry scaffolding
+(`.verdaccio`, `verdaccio`, the `local-registry` target); pins `nx` and every `@nx/*` to one exact version, by
+default the newest published in the major already in use (`--nx <version>` overrides it); installs; and runs
+`npm audit fix` (never `--force`) until `mnci ci audit` passes, up to four passes. Run on a copy of a real
+hand-built workspace it moved Nx 23.1.1 to 23.3.0 and the audit gate passed after one pass.
+
+**`--kinds`** records each project's mnci kind as a `type:<kind>` tag, in its `project.json` or the `nx.tags` of
+its `package.json` (`mnci projects` shows it). The kind is read from the project itself: an `index.html` next to
+React, an `engines.vscode`, an `OutputType` of `Exe`, a `package main`, `lib/main.dart`. Where two kinds fit (a
+library that is internal or published, a script that is an app or a library) the project is listed with the
+guess and why, and **not** tagged; name it with `--kind <dir>=<kind>` (repeatable) to accept or change the
+guess, and the step exits non-zero until every project has a kind. A project that already has a `type:*` tag
+keeps it, even one that is not an mnci kind name. Nothing is regenerated and no target is written: Nx infers an
+npm project's targets from its scripts. Needs a clean git tree.
+
+**`--overlay`** applies the mnci overlay (release config, `.npmrc`, commitlint, the curated root scripts and the
+CI pipeline) to a repository that has an `nx.json`. It is `mnci upgrade` behind adoption's guard rails: it
+refuses an unclean git tree, takes the same flags (`--scope`, `--registry`, `--organization`, `--project`,
+`--artifacts-feed`, `--agent`, `--variable-group`, `--npm-auth`, `--ci`, `--test-runner`) and fills `--ci` and
+`--test-runner` from what the repository already has (its pipeline files, `jest` or `vitest` in the root
+manifest). The existing pipeline goes through the legacy migration: steps mnci does not recognise are kept in
+the three `# mnci:slot` blocks, the ones it does are replaced by `mnci ci <phase>`, and what cannot be carried
+over is listed. Scope, registry and agent have no safe guess, so they are asked for by flag. Adopt does not
+install Nx: a repository with no `nx.json` is told to run `npx nx@latest init` first.
+
 ## `mnci upgrade`: re-applying the overlay to an existing workspace
 
 Every fix to `workspace-overlay/overlay.use-case.ts` — a release-config correction, a CI guard rewritten,