…ory (#36272)

## Current Behavior

The `23-1-0-set-tsconfig-root-dir-for-ts6` migration skips any tsconfig
whose inferred common source directory already equals the tsconfig's own
directory, on the assumption that TypeScript 6 infers the same value so
no pin is needed.

That assumption only holds for the program the config declares.
Inference is per-program: a tool that compiles a subset of the config's
files re-infers the common directory from that subset alone. Concretely,
ts-jest with its `isolatedModules` option builds a program per test
file, the common directory collapses to that file's folder, and
TypeScript 6 hard-fails with:

```
error TS5011: The common source directory of 'tsconfig.spec.json' is './src/document-links'.
The 'rootDir' setting must be explicitly set to this or another path to adjust your output's file layout.
```

This is not hypothetical — it broke nx-console's CI on its nx
23.1.0-rc.0 migration (nrwl/nx-console#3175): the `nxls-e2e` and
`nx-mcp-e2e` projects' spec tsconfigs include the root-level
`jest.config.ts` alongside `src/**`, so their inferred dir equals the
config dir and the migration skipped them; every atomized `e2e-ci` jest
task then failed with TS5011. Ironically, sibling projects whose include
starts at `src/**` were pinned fine — including the root-level
`jest.config.ts` is exactly what exempted the broken ones.

## Expected Behavior

Every non-composite candidate (no `rootDir`, has an emit-gate option,
has input files) gets an explicit `rootDir` pin — the file-derived
directory when it differs from the config dir (as before), and `.` when
it doesn't (new). The pinned value is exactly what TypeScript 5 inferred
for the declared program, so compilation and emit layout are unchanged;
single-file programs can no longer re-infer a different root.

Composite configs keep the previous behavior (never pinned from files,
only shielded from an `extends` base pin) — their `rootDir` defaults to
the tsconfig directory in both TS5 and TS6 for any file subset, so they
are genuinely safe.

Implementation notes:

- The `own-dir` analysis kind is gone: the `commonDir == config dir`
case now falls through to the normal `write` path (producing `.`), and
composite gets its own `composite` kind. The phase-3 shield loop now
only processes composite configs, since every non-composite candidate is
pinned directly in phase 2.
- The migration entry is re-stamped `23.1.0-beta.8` → `23.1.0-rc.1` so
workspaces that already migrated to rc.0 run it again on their next `nx
migrate`. The writes are idempotent (`rootDir` present → untouched), so
re-running over already-pinned workspaces is a no-op.
- Added a regression spec modeled on the nx-console shape: a spec
tsconfig whose include spans its own directory root (`jest.config.ts` +
`src/**`) must come out with `"rootDir": "."`. All 10 specs pass.

## Related Issue(s)

Discovered via the coordinated nx 23.1.0-rc.0 migration (nx-console CI
failure on nrwl/nx-console#3175; fixed there manually with the same
`"rootDir": "."` pins this migration now writes).

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Migrate-nrwl-repos-to-nx-23.1.0-rc.0-b8c94700)
<!-- polygraph-session-end -->

…eywords (#36326)

## Current Behavior

`nx release changelog` extracts issue references from the commit body
with a bare `/(#\d+)/gm` regex, so **every** `#number` in a squashed PR
description becomes an issue link in the changelog — including other
repos' issue numbers.

For example, the [23.1.0 release
notes](https://github.com/nrwl/nx/releases/tag/23.1.0) contain:

> **rspack:** support @rspack/core@2 and @rsbuild/core@2 (multi-version
compliance) (#35682, #35764, #13420, #781)

where `#13420` is actually `web-infra-dev/rspack#13420` and `#781` is
`privatenumber/tsx#781` — upstream issues discussed in the PR
description, rendered as (bogus) `nrwl/nx` issue links. The same release
also picked up `nrwl/nx-console#3175`, `react/react#418`, and
`web-infra-dev/rspack#2292`, plus noisy same-repo PR mentions that were
merely referenced in prose.

## Expected Behavior

Issue references are only extracted from the commit body when linked via
a GitHub closing keyword (`Fixes #123`, `Closes #123`, `Resolves: #123`,
...) — the same rule GitHub itself uses to auto-link and close issues.
Cross-repo forms (`owner/repo#123`), markdown links to other repos, and
casual same-repo mentions no longer produce changelog references.

Subject-line extraction (the PR number in `(#123)` and inline issue
refs) is unchanged. Both regular commits and version plans go through
the same `extractReferencesFromCommit` function, so this fixes both
paths.

## Related Issue(s)

N/A

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Fix-nx-release-changelog-scraping-other-repos-issue-numbers-7967dd62)
<!-- polygraph-session-end -->

…eywords (#36326)

## Current Behavior

`nx release changelog` extracts issue references from the commit body
with a bare `/(#\d+)/gm` regex, so **every** `#number` in a squashed PR
description becomes an issue link in the changelog — including other
repos' issue numbers.

For example, the [23.1.0 release
notes](https://github.com/nrwl/nx/releases/tag/23.1.0) contain:

> **rspack:** support @rspack/core@2 and @rsbuild/core@2 (multi-version
compliance) (#35682, #35764, #13420, #781)

where `#13420` is actually `web-infra-dev/rspack#13420` and `#781` is
`privatenumber/tsx#781` — upstream issues discussed in the PR
description, rendered as (bogus) `nrwl/nx` issue links. The same release
also picked up `nrwl/nx-console#3175`, `react/react#418`, and
`web-infra-dev/rspack#2292`, plus noisy same-repo PR mentions that were
merely referenced in prose.

## Expected Behavior

Issue references are only extracted from the commit body when linked via
a GitHub closing keyword (`Fixes #123`, `Closes #123`, `Resolves: #123`,
...) — the same rule GitHub itself uses to auto-link and close issues.
Cross-repo forms (`owner/repo#123`), markdown links to other repos, and
casual same-repo mentions no longer produce changelog references.

Subject-line extraction (the PR number in `(#123)` and inline issue
refs) is unchanged. Both regular commits and version plans go through
the same `extractReferencesFromCommit` function, so this fixes both
paths.

## Related Issue(s)

N/A

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Fix-nx-release-changelog-scraping-other-repos-issue-numbers-7967dd62)
<!-- polygraph-session-end -->

…eywords (#36326)

## Current Behavior

`nx release changelog` extracts issue references from the commit body
with a bare `/(#\d+)/gm` regex, so **every** `#number` in a squashed PR
description becomes an issue link in the changelog — including other
repos' issue numbers.

For example, the [23.1.0 release
notes](https://github.com/nrwl/nx/releases/tag/23.1.0) contain:

> **rspack:** support @rspack/core@2 and @rsbuild/core@2 (multi-version
compliance) (#35682, #35764, #13420, #781)

where `#13420` is actually `web-infra-dev/rspack#13420` and `#781` is
`privatenumber/tsx#781` — upstream issues discussed in the PR
description, rendered as (bogus) `nrwl/nx` issue links. The same release
also picked up `nrwl/nx-console#3175`, `react/react#418`, and
`web-infra-dev/rspack#2292`, plus noisy same-repo PR mentions that were
merely referenced in prose.

## Expected Behavior

Issue references are only extracted from the commit body when linked via
a GitHub closing keyword (`Fixes #123`, `Closes #123`, `Resolves: #123`,
...) — the same rule GitHub itself uses to auto-link and close issues.
Cross-repo forms (`owner/repo#123`), markdown links to other repos, and
casual same-repo mentions no longer produce changelog references.

Subject-line extraction (the PR number in `(#123)` and inline issue
refs) is unchanged. Both regular commits and version plans go through
the same `extractReferencesFromCommit` function, so this fixes both
paths.

## Related Issue(s)

N/A

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Fix-nx-release-changelog-scraping-other-repos-issue-numbers-7967dd62)
<!-- polygraph-session-end -->

(cherry picked from commit d7312d2)