fix: support React 18 type peers

[olliethedev]

Summary

• widen @types/react and @types/react-dom peers to match YAR's React 18/19 runtime support
• prepare patch release 1.3.1
• add a package metadata regression test

Validation

• pnpm build
• pnpm lint
• pnpm test -- --run (80 tests)
• pnpm typecheck
• packed-package npm resolution with React/types 18.3 and 19.2 cohorts

Required by better-stack-ai/better-stack#167 review feedback.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: efd74baefb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Exclude React 18 typings that lack React.JSX

When a consumer is pinned to an early @types/react 18.x release, this range now declares the installation supported even though the emitted public declarations reference React.JSX.IntrinsicElements from src/router.ts and src/define.ts; those older typings expose only the global JSX namespace, so TypeScript reports that React has no exported member JSX. Constrain the React 18 lower bound to a release that provides React.JSX (and compile-test that lower bound), or avoid emitting React.JSX in the public types.

Useful? React with 👍 / 👎.