fix(codemod): warn about retained React JSX callers - #2657

Summary

Warn when an unchanged React JSX component directly renders a relative JSX import that the codemod will rename to an Octane component. Report the edge on the retained caller and selected leaf.

Selecting only the leaf in a standard React JSX project rewrites the caller's import to .tsrx. Production React SSR then rejects the Octane element returned by the leaf. The existing server-render advisory covers direct calls to the React DOM renderer. A plain React component return can reach the same failure through an ancestor.

Validation

• pnpm format:check
• pnpm typecheck
• pnpm test
• Production React SSR reproduced the retained-caller failure. An authored OctaneCompat control rendered successfully.
• All 1,403 codemod and CLI tests, including a dual-export deduplication regression, plus codemod package typecheck, targeted formatting, changeset validation, pnpm sync, and git diff --check.
• The focused project checks cover default and named imports, JSX runtime aliases, native JSX, a shadowed binding, a type-only import, an authored bridge, and the warning in write mode.
• Concision review. Reuse the existing export, JSX runtime, and resolved rename checks. The new binder runs only on retained JSX issuers with a pending path rewrite and a plausible explicit JSX extension.
• Performance review is inapplicable to runtime output. This adds an advisory to the migration tool.

Risk / follow-ups

The check follows explicit relative JSX paths and direct exported returns under the standard resolver. Bundler-only aliases can supply a different renderer, so this is an advisory. The recipe-free replay matched all 7,902 rows, including the 1,361 clean Strong results on the base.

Provenance

• An agent produced this diff (agent-authored)

Codex task · host com-79386

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}