…d beta

## Current Behavior

Angular generators install vitest 5. `@angular/build` >= 21 skips the vitest pre-seed, so `@nx/vitest` picks the latest, and `@nx/angular` then rejects it against `^4.0.8`.

## Expected Behavior

Version selection takes the framework being configured, not just installed deps. Analog is added in the same pass, so it is not in package.json yet when the version is chosen.

## Related Issue(s)

NXC-5032

## Current Behavior

The codemod repoints `vitest/suite` and `vitest/runners` to modules that do not export their symbols, so migrated files no longer compile. Version selection caps Angular at vitest 4 only when nothing is installed yet and without intersecting the vite floor, and the migration gates miss `@angular/build` and the browser providers, which peer vitest 4.

## Expected Behavior

Rewrite a specifier only when every one of its v4 exports landed in one v5 module, and hand the rest to the paired prompt. Compute the framework cap before the installed-version branch, intersect it with the vite floor, and refuse an installed vitest the framework cannot take. Gate the package updates on `@angular/build` and the browser providers too.

Selection now takes the vite range rather than a major, so a `^6.9.0` workspace is no longer read as `6.0.0`. The migration declares the vite already resolved in the workspace instead of pinning 8.

## Related Issue(s)

NXC-5032

## Current Behavior

The version ladder is spread over three structures, and callers thread a `uiFramework` flag down so selection can predict a dependency the same pass is about to write. The migration reimplements the gitignore rule and reads and parses each file twice.

## Expected Behavior

The configuration generator writes the analog packages before init, so selection reads only `package.json` and the flag is gone. One ordered compat table replaces the vite floor map, the version map and the latest-versions record. `getInstalledViteVersion` returns undefined when vite is absent rather than reporting the default as installed, matching `@nx/vite`.

The migration reuses `addVitestTempFilesToGitIgnore`, visits each file once, and no longer reports an unrelated `sequential` member. `addVitestTempFilesToGitIgnore` appends instead of running `stripIndents` over the whole file.

## Related Issue(s)

NXC-5032

## Current Behavior

`updateGitIgnore` prepends a newline before every entry, so a workspace without a `.gitignore` gets one that opens with a blank line. `@nx/vitest` used to run `stripIndents` over the whole file afterwards, which hid it.

## Expected Behavior

The separator is only added between entries.

## Related Issue(s)

NXC-5032

## Current Behavior

A namespace import or a star re-export of a removed entry point is repointed without checking symbols, so `import * as reporters from 'vitest/reporters'` moves to `vitest/node`, which does not export everything it did. The `sequential` scan reports any property with that name, including unrelated application code.

## Expected Behavior

Only declarations that name their bindings are repointed; the rest go to the migration prompt. `sequential` is reported only in an options object passed to a test or suite call.

## Related Issue(s)

NXC-5032

…CI Rerun]

## Current Behavior

Both pages label the Atomizer link with the product name alone. The Jest intro links test splitting to the unit and e2e section rather than the option that turns it on.

## Expected Behavior

The link reads task splitting (Atomizer), and both intros point at the plugin options section where `ciTargetName` lives.

## Related Issue(s)

NXC-5032