Share one layout owner
List and detail consume one project record without duplicate reads.
0.11.2AUGUST 2026
OWN · INVALIDATE · RELEASE
Review the pressure.
Keep one owner.
Three unrelated server-data fixtures reuse ordinary state and owned effects. None requires a shared request registry, subscriber graph, or cache.
3Independent fixtures
0New runtime concepts
0 BBrowser increase
0.11.2Reuse ownership.
COORDINATION DECISION
Reuse ownership.
Reject speculative cache.
Own one route effect
TanStack-shaped loading reduces to explicit state and one request owner.
Invalidate dependencies
Answer-shaped page and order changes replace stale effect ownership.
Reuse owned effects
Existing dependency invalidation and cleanup cover every journey.
Require repeated pressure
No fixture has independent subscribers requesting the same key.
Skip request registries
No cache, invalidation graph, subscriber set, or scheduler ships.
UPGRADE
Keep server data explicitly owned.
$
npm install @kudzujs/core@^0.11.2