Move the conformance submodule from v21.2.2 to v22.0.0-rc.2 and
regenerate the extracted fixtures + snapshot against the v22 specs.

Pass rate is 1235/1264 (97.7%); the 29 new failures are genuine v22
feature/behavior additions not yet implemented in OXC, tracked as
follow-up: the `in` expression operator, `@switch` exhaustive
`@default never`, `@defer` `idle(timeout)`, `data-*` binding prefixes,
`@let` source spans, and several ShadowCss `:host`/comment cases.

Fixture hygiene fixed along the way:
- store `file_path` repo-relative instead of an absolute home dir
- restore the trailing newline on generated fixtures
- drop orphaned shadow_css_polyfills_spec.json (spec removed in v22)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22's parser_spec adds "should throw on invalid in expressions",
exercising error recovery around the `in` operator. OXC parsed `in`
correctly as a relational operator but mishandled three error cases:

- A bare keyword in primary position (`in`, `in foo`) was silently
  treated as an identifier read. Angular treats only identifier tokens
  as reads, so a keyword here reports "Unexpected token <kw>".
- Running out of input mid-expression (`'foo' in`) produced a silent
  EmptyExpr. Angular reports "Unexpected end of expression: <input>".
- The error formatter now appends `[<source>]` to the end-of-expression
  message to match Angular's getParseError output.

Empty input still parses error-free (parse_chain guards via the token
list being empty). Conformance expression_parser: 270/270.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 lets the `idle` deferred trigger take an optional timeout
parameter (`on idle(100)`), mirroring `timer`. Previously OXC rejected
any parameter on `idle`.

- Add `timeout: Option<f64>` to `R3IdleDeferredTrigger`.
- Parse zero-or-one parameter in the `idle` arm via `parse_deferred_time`,
  matching the reference error strings for >1 param and unparseable time.
- Humanize `['IdleDeferredTrigger', <timeout>]` when present.

Conformance r3_transform: 165 -> 168. Emit threading of the timeout into
the defer config is deferred (not exercised by these AST-level specs).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 removed `data-` prefix normalization: binding syntax
(`bind-`, `on-`, `bindon-`, `ref-`, `let-`) is now matched against the
raw attribute name. So `data-ref-a`, `data-let-a`, `data-on-event`, and
`data-bindon-prop` are plain text attributes, and an interpolated
`data-prop="{{v}}"` keeps its `data-` prefix in the bound attribute name.

Drop `normalize_attribute_name` and the data- strip in
`parse_binding_prefix`, using the raw name throughout.

Conformance r3_transform: 168 -> 173.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 ends a `@let` declaration's sourceSpan at the end of the
terminating semicolon (`end = endToken.sourceSpan.end`). OXC ended the
span just before the `;`, and the conformance humanizer additionally
stripped a trailing `;`. Both now keep the semicolon.

Conformance html_parser 85->86, r3_transform 173->174.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 simplified ShadowCss shimming. Three behavior changes,
bringing the shadow_css conformance subsystem back to 100%:

- Comment removal no longer appends an extra newline; only the newlines
  inside the comment are preserved (`/* c */ b {}` -> ` b[contenta] {}`).
- A `:host(...)` whose argument is a selector list (top-level commas) is
  left literal and prefixed with the content attribute
  (`:host(.a, .b)` -> `[contenta]:host(.a, .b)`), instead of being split.
- A `:host-context` without a non-empty argument list (bare,
  `:host-context()`, `:host-context( )`) is no longer a context selector;
  it stays literal and is content-scoped. `:host` is no longer mangled
  inside `:host-context` (mirrors `/:host(?!\-context)/`).

Drops the now-unused data-/host-attr conversion fallback and updates two
comment integration tests to the v22 output.

Conformance shadow_css: 160 -> 169 (100%).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular classifies `<script>`/`<style>` as special (content-extracting)
elements by their lowercased element name, which for SVG content is
namespaced (`:svg:style`) and therefore not matched. OXC checked the raw
name before namespace resolution, so an SVG `<style>` was wrongly
stripped. Gate the special handling on the HTML namespace.

Conformance r3_transform: 174 -> 175.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 added `@default never;` inside `@switch` as an exhaustive
type-narrowing marker. It is lexed as a block named "default never",
terminated by `;` instead of a `{ ... }` body, and lowers to a
`SwitchExhaustiveCheck` node on the switch (no runtime output).

- Lexer: emit BlockOpenEnd + BlockClose for `@default never;` (and
  `@default never(expr);`), mirroring the reference `_consumeBlockStart`.
- AST: add `R3SwitchExhaustiveCheck` and `SwitchBlock.exhaustive_check`,
  with a visitor hook visited after the case groups.
- Transform: intercept the "default never" block (optional expression,
  no body) and attach it as the exhaustive check.
- Humanize `SwitchExhaustiveCheck` after the case groups.

Conformance: html_lexer, html_parser and r3_transform back to 100% —
the full suite is now 1264/1264 (100%) against v22.0.0-rc.2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

All 1,264 extracted assertions pass after implementing the v22 features.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Bump the npm @angular/* dependencies to 22.0.0-rc.2 in the packages that
validate compiler behaviour against the real Angular compiler — the
NAPI package, the e2e app and the output-parity `compare` harness — plus
the playground. This keeps the npm side aligned with the conformance
submodule (also v22.0.0-rc.2).

The pinned real-world benchmark apps (typedb-web, bitwarden) stay on
their 21.2.x snapshots; they are perf fixtures, not compat validation,
and bumping a full app to a pre-release would risk breaking their builds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Angular v22 broadened `specializeControlProperties` beyond `formField`:
`formControl`, `formControlName` and `ngModel` (including two-way
`[(ngModel)]`) now also emit the paired `ɵɵcontrolCreate()` (create) and
`ɵɵcontrol()` (update) instructions.

- ingest: detect the control property across `[..]` property bindings,
  two-way `[(ngModel)]`, and static `formControlName=`/`ngModel`
  attributes, and add the `ControlCreateOp` after element creation.
- binding_specialization: add the `ControlOp` update after the property
  update for `formField`/`formControl`/`formControlName`/`ngModel`, and
  after the two-way property update for `[(ngModel)]`.

Brings the e2e compare harness to 100% parity (686/686) against
@angular/compiler 22.0.0-rc.2. Snapshots updated for the two-way ngModel
fixtures (now emit controlCreate + control).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The compare harness compiled OXC without an `angularVersion`, so OXC fell
back to its conservative legacy default (e.g. legacy safe-navigation
`?.`) while comparing against a newer @angular/compiler. After the v22
bump this surfaced as safe-navigation mismatches. Thread the installed
@angular/compiler VERSION into OXC's TransformOptions so version-gated
emit aligns with the baseline it's compared against.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The extended control-property specialization (ɵɵcontrolCreate/ɵɵcontrol for
formControl/formControlName/ngModel, including two-way [(ngModel)]) is a
v22 emit change; v21 only did this for [formField]. Emitting the extra
instructions against a < v22 runtime would diverge.

Gate the extended set behind `AngularVersion::supports_extended_control_
properties()` (major >= 22), keeping `formField` unconditional as the v21
baseline. Per the crate convention an unknown version assumes latest, so
the default (and the e2e compare harness, which now targets v22) is
unchanged. Threaded through both the ingest control-create detection and
the binding-specialization control-update insertion.

Adds a version-gate regression test: `[(ngModel)]` emits only
ɵɵtwoWayProperty on v19/v20/v21, and additionally ɵɵcontrolCreate/ɵɵcontrol
on v22+ and when the version is unknown.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The e2e HMR fixture app and the playground are runtime apps; booting them
on Angular v22.0.0-rc.2 needs app/vite-plugin migration work that is out
of scope here (the v22 runtime fails to render, timing out every
Playwright HMR test). Revert those two to v21.2.x.

The compiler-validation surface stays on v22: the `compare` harness still
diffs OXC output against @angular/compiler@22.0.0-rc.2 (686/686), and the
NAPI package keeps its v22 compiler-cli. Both reverted apps use none of
the version-divergent template features, so the (v22-default) compiler
emits v21-identical output for them; the local HMR e2e suite passes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>