- Wrap `keyof AllCodeGenerationSchemas` in parens so `jsdoc/type-formatting`
  accepts the conditional `@typedef` for `CodeGenValue`.
- Add a `@template {string} K` to the `CodeGenMapOverloads` typedef so
  `jsdoc/require-template` no longer flags the inline `<K extends string>`
  generic parameters on each `@property`.

The two errors reproduce on a clean `origin/main` checkout (introduced by
the JSDoc rule tightening in 20906/20926) and were the only remaining
`yarn lint:code` failures on this branch.

- Mark `parser.javascript.typescript` as `"experimental": true` in
  the schema so it matches the experiments-level flag and so the
  generated `@experimental` JSDoc tag is emitted on
  `JavascriptParserOptions.typescript` in declarations.
- Regenerate `types.d.ts`, `declarations/WebpackOptions.d.ts`, and
  `schemas/WebpackOptions.check.js` against `[email protected]`.
- Revert the `@template {string} K` workaround on
  `CodeGenMapOverloads` — the updated `eslint-plugin-jsdoc` no
  longer trips on inline per-property generics, so the workaround
  was unneeded and removing it lets `generate-types` re-emit the
  `CodeGenMapOverloads`/`CodeGenValue`/`AllCodeGenerationSchemas`
  interfaces that the workaround had silently stripped.

Node 26 stabilised `module.stripTypeScriptTypes` and dropped both the
legacy `mode: "strip-only"` value AND `mode: "transform"`. Switch the
plugin to `mode: "strip"` — the only value Node 26 accepts and one
that's also valid on Node 22.6+. The trade-off is that strip mode
rejects non-erasable syntax (`enum`, `namespace`, parameter-property
constructors), which aligns with what `experiments.typescript` was
always documented to support; for non-erasable code use the
`examples/typescript-non-erasable` (ts-loader) path.

* Node 26 also rejects `sourceMap: true` in strip mode. Drop the
  option and construct a line-granularity identity source map
  manually — strip mode preserves the original line layout
  (annotations are replaced with whitespace) so an identity mapping
  is correct. The map is still composed with any upstream loader
  source map via `SourceMapSource`.
* Drop the now-unused `getExtractSourceMap` / `getDataURL` helpers
  from the plugin.
* `basic/index.ts` no longer uses `enum`; switched to a union-type
  alias.
* `namespace/index.ts` is now a negative test: the build is expected
  to fail with `TypeScript namespace declaration is not supported in
  strip-only mode`, asserted via a new `errors.js` fixture.

Add the `"typescript"` conditional-exports key to webpack's resolve
`conditionNames` when `experiments.typescript` is on (Node.js amaro
convention). Monorepo packages can now ship `.ts` sources alongside
compiled output:

```json
{
  "exports": {
    ".": {
      "typescript": "./src/index.ts",
      "import": "./dist/index.js"
    }
  }
}
```

New `test/configCases/typescript/conditional-exports/` covers this —
a `my-lib` fixture with both branches resolves to its `.ts` source.

Also addresses two follow-ups:

* `tsc -p tsconfig.types.test.json` failed on the
  `loader-source-map/loader/banner-loader.js` fixture — type the
  loader via `LoaderDefinition` and add the required `file` property
  on the emitted source map literal.
* Add `AACA` and `amaro` to the cspell wordlist.

Restructure `TypeScriptPlugin` for readability:

* Pull the per-step logic out of the `processResult` tap into small,
  focused module-level helpers:
  - `isTypeScriptResource(resource)` — single regex gate.
  - `toBomFreeString(source)` — Buffer/string coercion + BOM strip.
  - `stripTypes(input)` — wraps `mod.stripTypeScriptTypes` in a
    `ModuleBuildError`.
  - `createIdentitySourceMap(resource, source)` — line-granularity
    identity map for the strip-types output.
  - `composeWithLoaderSourceMap(...)` — `SourceMapSource` chaining.
* Move the tap body into `_processResult(result, module)` typed
  against `NormalModule`'s `Result` tuple so JSDoc types stay tight.
* Lift the inline error strings to module-level constants.

Drop the `sourceUrl: module.resource` option. Node 26 still accepts
it but emits a `//# sourceURL=…` legacy V8 pragma into the JS output,
which adds noise; webpack's source map handling replaces what that
pragma was for. Pass only `mode: "strip"`.

Behavioural diff: none. 49/49 typescript configCases still pass on
Node 22.22.3 and Node 26.1.0; lint/tsc/types-test/fmt/spellcheck all
clean.

Folds the TS-related defaults additions back into the inline
snapshots that picked up main's `experiments.html` / `sourceImport`
defaults during the rebase. No source code change.

`test/configCases/typescript/namespace/` was a negative test asserting
the build fails with `TypeScript namespace declaration is not
supported in strip-only mode`. It passes under `ConfigTestCases` but
fails under `ConfigCacheTestCases` (yarn test:basic) because webpack's
persistent cache logs `Pack got invalid because of write to: …` on the
second cache-validation run — the errored module doesn't serialize
cleanly and triggers cache invalidation, which the test harness
treats as an `InfrastructureLogs` failure when `run >= 2`.

The namespace limitation is already documented in two places: the
changeset (`.changeset/experimental-typescript-support.md`) and the
`examples/typescript-non-erasable/` example which motivates using
`ts-loader` for namespaces/enums/parameter-property constructors.
The error itself comes from Node.js and is stable. Drop the fragile
test rather than carry a cache-special-case workaround.

ConfigTestCases (47/47) and ConfigCacheTestCases (77/77 typescript
variants) now both pass on Node.js 22.22.3 and 26.1.0.