[KidkArolis]

Query ownership and event rules were re-derived across fetch commits, row snapshots, and realtime replay. Graph freshness adoption and prefetch expiry were also split between Figbird and relational refs.

This compiles response rebasing, row ownership, and event policies once per query, including the store and inspector's remaining realtime checks. The rules stay in private storage so state subscribers retain the original maintenance shape. Fetch commits separate planning from cache application at the existing atomic boundary; the planner decides which pending mutations participate in a query and which lanes need settlement deferral. Mutation acknowledgements still precede planning, and notifications still follow the cache commit.

Each relational query has one lifetime manager for reader/preparation/prefetch leases, Suspense adoption, and prefetch expiry. The lifetime owns the root Suspense entry and observes actual graph starts. Legacy hooks and their contracts are retained.

Validation:

• npm run tsc, npm run lint, npm run ava, and npm run test pass; all 440 tests pass.
• Committed tests cover prefetch expiry, replacement, timer cancellation, and disposal, plus the 1,024-combination comparison against the original policy rules.
• Regression coverage verifies the subscriber-visible maintenance shape and snapshot fetches during pending optimistic writes. The original state snapshots are restored.
• npm run package:check verifies ESM, CommonJS, declarations, type-only exports, legacy hooks, and private exports.

[cursor]

Risk: medium. Approved; Cursor Bugbot completed with no findings, and no Security Agent check was present. No reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver - Risk Based}