effectlisted

# Effect Use current Effect v4 APIs and the production defaults in this skill. Established project conventions still take precedence unless the task is explicitly changing them. ## Source Rule Check these before guessing: - the nearest `AGENTS.md` and any project-local Effect practices doc - the project-pinned `effect` package source and version - current upstream Effect source when the installed package does not answer the question ## Branch Chooser Read only the branch references that match the task. - Data models, schemas, brands, variants, optional keys, or decoders: read `references/SCHEMA.md`. - Services, module surfaces, layers, runtime wiring, errors, `Effect.fn`, or test services: read `references/SERVICES_LAYERS.md`. - Runtime config, env variables, `ConfigProvider`, or `layerConfig`: read `references/CONFIG.md`. - Retry, repeat, polling, backoff, jitter, rate-limit-aware policies, or pass loops: read `references/SCHEDULING.md`. - Memoization, per-key TTL caches, deduplicating concurrent lookups, or request batching: read `references/CACHING.md`. - Streams, event sources, async iterables, queues/pubsubs, pagination, backpressure, or stream consumers: read `references/STREAMS.md`. - Outgoing HTTP calls, Effect HttpClient, status handling, or HTTP rate limiting: read `references/HTTP_CLIENTS.md`. - Effect tests, time, sleeps, concurrency synchronization, or fakes: read `references/TESTING.md`. If a task spans several branches, read all matching files before ed