Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/react-on-rails/package.json`:
- Around line 62-67: The peer dependency range for "@tanstack/react-router" is
too loose (">= 1.0.0") and can pull in breaking v2+ changes; update the
peerDependencies entry for "@tanstack/react-router" to constrain to v1.x (for
example ">=1.0.0 <2.0.0") so consumers cannot install incompatible v2+ releases
that break uses of internal APIs like router.__store.setState and router.ssr.

In `@packages/react-on-rails/src/tanstack-router/clientHydrate.ts`:
- Around line 44-47: The initialization forcibly setting status to 'idle'
prevents the later condition that calls router.load() from ever running; remove
the status override so the initial state uses the router's real status and then
unconditionally call router.load() on first client render (respecting router.ssr
= true behavior) to enable client-side navigation — update the clientHydrate
initialization that assigns status and resolvedLocation and ensure router.load()
is invoked (call router.load() directly or remove the status check gating it) so
that Router.load() executes after the first render.

In `@packages/react-on-rails/src/tanstack-router/index.ts`:
- Line 39: The public entrypoint currently only re-exports types
(TanStackRouterOptions, DehydratedRouterState) and the sync factory but omits
the async SSR helper; add an explicit export for serverRenderTanStackAppAsync so
consumers can import it from the package surface (e.g. export {
serverRenderTanStackAppAsync } from './serverRenderTanStackAppAsync' or from the
module where it's implemented) and similarly ensure the same export is added in
the other export block referenced (lines ~106-117) so the async helper is
available from both public entrypoints; reference the symbol
serverRenderTanStackAppAsync when adding the export.

---

Nitpick comments:
In `@packages/react-on-rails/src/tanstack-router/types.ts`:
- Around line 11-21: The type for search is too narrow (Record<string, string>)
and rejects valid TanStack Router schemas; update the search typing used in
matchRoutes signature and in state.location (and the other occurrences around
the same area) to a wider type such as Record<string, unknown> (or
Record<string, any>) so non-string search values are accepted; locate the
matchRoutes declaration and the state { location { search } } type blocks and
replace the Record<string, string> occurrences with the wider type.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/api-reference/view-helpers-api.md`:
- Line 27: Update the wording for the renderer-function sentence in the
component_name description: change "dom (client side only)" to "DOM (client-side
only)" and hyphenate "renderer function" consistently where applicable; ensure
the phrase still clarifies that a "renderer function" takes a third parameter of
a DOM ID and that it's client-side only, referencing the symbol component_name
and the term "renderer function"/"Render-Function".

In `@docs/building-features/tanstack-router.md`:
- Around line 13-15: Update the installation code block in the tanstack-router
docs to be package-manager-agnostic by adding npm and yarn variants alongside
the existing pnpm command; specifically replace the single-line pnpm install
snippet with three lines showing "npm install `@tanstack/react-router`", "yarn add
`@tanstack/react-router`", and "pnpm add `@tanstack/react-router`" in the same
fenced bash block so readers can use their preferred package manager.

In `@packages/react-on-rails/src/tanstack-router/serverRender.ts`:
- Around line 11-27: validateRouterInternals currently only checks
__store.setState and matchRoutes but not the shape of router.state.location,
which later leads to unsafe dereferences of router.state.location.pathname and
.search; update validateRouterInternals to also verify router.state and
router.state.location exist and that location.pathname and location.search are
strings (or at least defined), and throw a clear compatibility Error (same style
as existing messages) mentioning validateRouterInternals and
router.state.location so callers get a helpful message if `@tanstack/react-router`
changes its location shape.

In `@react_on_rails/lib/react_on_rails/helper.rb`:
- Around line 583-588: Reorder and tighten the checks around client_props: first
handle nil (return if client_props.nil?), then validate its type (unless
client_props.is_a?(Hash) raise ReactOnRails::Error ...), and only after
confirming it's a Hash call client_props.empty? and return if empty; this
ensures client_props.empty? is never invoked on non-Hash scalars—refer to the
local variable client_props and the raised ReactOnRails::Error for where to
apply the change.
- Around line 590-596: The code in the react_on_rails helper incorrectly raises
ReactOnRails::Error when render_options.props is a JSON string but clientProps
exists; instead, update the merge logic in the block referencing existing_props
and render_options.props to accept a JSON-string props by parsing the JSON
string into a Hash (or safely converting it) before merging clientProps,
handling JSON parse errors by raising the current error only if parsing fails;
ensure the same merge path is used whether props started as a Hash or a JSON
string so react_component’s documented JSON-string support remains compatible.