Does Qwik automatically invalidate cached server component HTML when props change?

Goal

Determine whether Qwik treats a changed server component input prop as a cache miss, or whether cached HTML remains valid until an explicit invalidation occurs.

Constraints and uncertainty

Qwik derives server component cache keys from input signatures, and available documentation describes revalidation as dependent on explicit actions or signals rather than automatic purges when external data changes. The behavior for non-deterministic props and dynamic request contexts is unspecified. Assume Qwik v1.x stable server components.

Open questions

• Does a changed prop value automatically expire the cached server component output?
• Which explicit action or signal triggers cache invalidation when external data updates?
• How should cache keys be constructed for non-deterministic props to avoid stale HTML?