Qwik Router ↔️ useParams: Will route parameters survive hydration?

Goal

Ensure that dynamic route parameters (e.g., /post/[id]) are consistently available after server‑side rendering and client‑side hydration in a Qwik application.

Context & Constraints

QwikRouter extracts dynamic segments on the server and injects them as props into the component during SSR. The generated HTML serializes these props into the component’s state. However, when a component initializes a useStore with non‑plain objects, the hydration process may not reapply the original parameter values, potentially leading to state mismatches.

Unresolved Decision

The documentation does not explicitly state whether route parameters are guaranteed to persist across the hydration boundary, especially for components that rely on useParams or useLocation hooks.

Specific Questions

• Does Qwik guarantee that route parameters remain intact after hydration when accessed via useParams?
• If not, what serialization or state‑management strategy should be used to preserve dynamic parameters across SSR and hydration?
• Are there known workarounds for components that initialize useStore with non‑plain objects to maintain parameter values?