Skip to content

Give retained stream policies consistent concrete identity #101

Closed

Description

@ueberBrot

Parent

Spec: Complete the review-driven Effect API Query 0.1.0 programme

What to build

Different bounds and refetch policies cannot satisfy each other from incompatible cached histories.

Acceptance criteria

  • Include normalized maxChunks and refetchMode in concrete accumulated-stream identity; omitted values normalize to unlimited/reset.
  • Key/options builders agree; default key calls remain usable and explicit defaults equal omitted defaults.
  • Verify wide-to-narrow and narrow-to-wide fetches, concurrent views, refetch behavior, and invalid policy handling including skipped queries.
  • Preserve concrete DataTags and root/branch/leaf/streamed-operation invalidation prefixes.
  • Publish matching compile-time fixtures and document the current cache-identity contract without exposing an internal tuple layout.

Metadata

Metadata

Assignees

Labels

ready-for-agentFully specified, ready for an AFK agent

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions