PR Checklist

@limitless-angular/sanity declared Angular 18 support, but the published visual-editing entry point included @let syntax that Angular 18.0.x consumers cannot compile.

Closes #

N/A - no linked issue.

What is the new behavior?

The visual editing insert menu and context menu templates now use @if (...; as icon) aliases instead of @let, preserving the rendered icon behavior while keeping the package compatible with the Angular 18 compiler floor promised by the peer dependency range.

The generated Angular compatibility consumer now covers the public Angular component surfaces more deliberately:

• Portable Text and Sanity image loading remain live runtime smoke checks with Playwright assertions.
• Preview kit and visual editing exported components are referenced from an inert ng-template, forcing Angular floor consumers to compile/link those component templates without changing runtime smoke behavior.
• The visual-editing lazy chunk is included in the Angular 18 floor build, so future template syntax regressions in that path should fail compatibility CI.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Testing:

• rg -n "@let" packages/sanity
• pnpm --filter @limitless-angular/sanity build
• pnpm --filter @limitless-angular/sanity test
• pnpm run compat:pack
• pnpm run compat:test --set angular-18-floor --skip-runtime
• node --test tools/angular-compat/*.test.mjs
• pnpm run compat:test --set angular-18-floor
• git diff --check

Negative verification:

• Temporarily reintroduced @let icon = iconFor(schemaType) in VisualEditingInsertMenuComponent, ran pnpm run compat:pack, then confirmed pnpm run compat:test --set angular-18-floor --skip-runtime failed under Angular 18.0.7 with Incomplete block "let icon". The temporary source edit was reverted and the clean artifact was repacked before the final passing run.

Screenshots: N/A - no intended visual change.

[Optional] What gif best describes this PR or how it makes you feel?