Write Effect TS

Write Effect code that matches the repo's existing style, keeps requirements explicit, and verifies API details against current docs before committing to an implementation.

Read Order

1. Read references/patterns.md before editing Effect code.
2. Read references/doc-map.md when you need topic-specific docs, upstream confirmation, or ready-made ctx7 queries.

Workflow

1. Inspect the repo first. Search for ServiceMap.Service, Effect.Service, Context.Tag, Effect.fn, Effect.gen, Schema.TaggedError, Schema.TaggedErrorClass, Config.schema, and it.effect.
2. Match the dominant local idiom. Do not mix service styles inside the same feature unless the repo already does.
3. If the repo has no strong local style, default to the effect-solutions house style summarized in references/patterns.md.
4. If effect-solutions is available, read the relevant topic before coding: