docs: replace the dashes in every list item with the punctuation each one needed

.agents/skills/create-adapter/SKILL.md

@@ -63,14 +63,14 @@ Create `packages/evlog/src/adapters/{name}.ts`. Read [references/adapter-templat
 
 The contract is `defineHttpDrain<TConfig>({ name, label, resolve, encode })`. You only ship two pieces of logic:
 
-1. **`resolve()`** — produce a fully-resolved config or `null` to skip. Use `resolveAdapterConfig` for the standard precedence (overrides → `runtimeConfig.evlog.{name}` → `runtimeConfig.{name}` → env vars). List `NUXT_{NAME}_*` before `{NAME}_*` in `ConfigField.env` for silent Nuxt compat; show only `{NAME}_*` in user-facing messages via `formatPublicEnvKeys`.
-2. **`encode(events, config)`** — a private `encode{Name}Request(events, config): HttpDrainRequest` returning `{ url, headers, body }` for a batch. HTTP transport, identity headers, retries, timeout, and error logging are handled by `defineHttpDrain` (via `httpPost`).
+1. **`resolve()`**: produce a fully-resolved config or `null` to skip. Use `resolveAdapterConfig` for the standard precedence (overrides → `runtimeConfig.evlog.{name}` → `runtimeConfig.{name}` → env vars). List `NUXT_{NAME}_*` before `{NAME}_*` in `ConfigField.env` for silent Nuxt compat; show only `{NAME}_*` in user-facing messages via `formatPublicEnvKeys`.
+2. **`encode(events, config)`**: a private `encode{Name}Request(events, config): HttpDrainRequest` returning `{ url, headers, body }` for a batch. HTTP transport, identity headers, retries, timeout, and error logging are handled by `defineHttpDrain` (via `httpPost`).
 
 Key rules:
 
 - **Single factory.** Export one `create{Name}Drain(overrides?: Partial<{Name}Config>)`. No dual-API factories: if a service has multiple ingest modes (logs vs events), expose them via a `mode` option (see PostHog).
-- **No HTTP code in the adapter.** Never call `fetch` directly. If the service truly needs custom transport (binary envelopes, non-HTTP), use `defineDrain` from `../shared/drain` instead — see `fs.ts` and `memory.ts`.
-- **Encode parity.** The standalone `sendTo{Name}` / `sendBatchTo{Name}` helpers must reuse the same private `encode{Name}Request()` and go through `sendEncodedDrainRequest(request, { label, source, timeout, retries })` — never a separate fetch path. `test/adapters/encode-parity.test.ts` pins this for a subset of adapters; add the new one to it (not every existing adapter is registered there yet — that's a gap, not a license to skip).
+- **No HTTP code in the adapter.** Never call `fetch` directly. If the service truly needs custom transport (binary envelopes, non-HTTP), use `defineDrain` from `../shared/drain` instead, see `fs.ts` and `memory.ts`.
+- **Encode parity.** The standalone `sendTo{Name}` / `sendBatchTo{Name}` helpers must reuse the same private `encode{Name}Request()` and go through `sendEncodedDrainRequest(request, { label, source, timeout, retries })`, never a separate fetch path. `test/adapters/encode-parity.test.ts` pins this for a subset of adapters; add the new one to it (not every existing adapter is registered there yet, and that is a gap, not a license to skip).
 - **No bespoke config resolution.** Always go through `resolveAdapterConfig`. Deprecated aliases (`token` → `apiKey`) go through `applyDeprecatedAlias`.
 - **Exported converters.** If the service needs a specific event shape, export `to{Name}Event()` / `build{Name}Payload()` helpers so they're testable independently.
 - **Edge-safe.** Adapters run on Cloudflare Workers: no `Buffer` (use `TextEncoder` + `btoa`, see `loki.ts`), no Node-only APIs. `fs.ts` shows the `isEdgeRuntime()` guard pattern when a runtime genuinely can't be supported.
@@ -114,7 +114,7 @@ Create `packages/evlog/test/adapters/{name}.test.ts`. Read [references/test-temp
 
 Non-negotiables from the test README:
 
-- Use `mockFetch()` / `getFetchCall` / `getFetchJson` / `getFetchHeaders` from `test/helpers/fetch.ts` — never hand-roll `vi.spyOn(globalThis, 'fetch')` boilerplate.
+- Use `mockFetch()` / `getFetchCall` / `getFetchJson` / `getFetchHeaders` from `test/helpers/fetch.ts`, never hand-roll `vi.spyOn(globalThis, 'fetch')` boilerplate.
 - Clean up any env vars the adapter reads in `afterEach`.
 - Test the exported pure helpers (`to{Name}Event`, `build{Name}Payload`, URL resolvers) directly, one `describe` per helper.
 
@@ -137,7 +137,7 @@ If the service is self-hostable, extend the local sandbox so the adapter can be
 - `packages/evlog/test/e2e/docker-compose.yml`: add the service
 - `packages/evlog/test/e2e/seed.mjs`: fan the seeder out to the new backend
 - `packages/evlog/test/e2e/README.md`: document it
-- Root `package.json` `sandbox:e2e` script — add the local env var if needed
+- Root `package.json` `sandbox:e2e` script: add the local env var if needed
 
 See the Loki and ClickHouse setups as references.
 
@@ -161,8 +161,8 @@ Create `{NN}.{name}.md` in the right category with the next available number. Us
 
 Edit `apps/docs/content/4.integrate/adapters/01.overview.md` in **two** places (follow the pattern of existing adapters):
 
-1. **Frontmatter `links` array** — add a link entry with icon and `/integrate/adapters/{category}/{name}` path, in category order
-2. **`::card-group` section** — add a card block in the matching position
+1. **Frontmatter `links` array**: add a link entry with icon and `/integrate/adapters/{category}/{name}` path, in category order
+2. **`::card-group` section**: add a card block in the matching position
 
 ## Step 8: Update the Public Skill
 

.agents/skills/create-adapter/references/adapter-template.md

@@ -140,8 +140,8 @@ export async function sendBatchTo{Name}(events: WideEvent[], config: {Name}Confi
 
 ## Customization Notes
 
-- **Auth style**: Some services use `Authorization: Bearer`, others a custom header (`X-API-Key`, ClickHouse's `X-ClickHouse-User`/`X-ClickHouse-Key`) or HTTP Basic (Loki + Grafana Cloud). Adjust `encode{Name}Request` — and prefer headers over query params so credentials never land in server-side query logs.
+- **Auth style**: Some services use `Authorization: Bearer`, others a custom header (`X-API-Key`, ClickHouse's `X-ClickHouse-User`/`X-ClickHouse-Key`) or HTTP Basic (Loki + Grafana Cloud). Adjust `encode{Name}Request`, and prefer headers over query params so credentials never land in server-side query logs.
 - **Payload format**: Raw JSON arrays (Axiom), wrapper objects (PostHog `{ api_key, batch }`), protocol structures (OTLP), NDJSON-style bodies (ClickHouse `JSONEachRow`). Adapt the encoder; export intermediate builders (`build{Name}Payload`) when the transformation is non-trivial.
-- **Non-HTTP transport**: If the service cannot fit `defineHttpDrain`, use `defineDrain<TConfig>({ name, resolve, send })` — see `fs.ts` and `memory.ts`.
+- **Non-HTTP transport**: If the service cannot fit `defineHttpDrain`, use `defineDrain<TConfig>({ name, resolve, send })`, see `fs.ts` and `memory.ts`.
 - **Deprecated aliases**: When renaming a config field (e.g. `token` → `apiKey`), keep both as `ConfigField` entries and map via `applyDeprecatedAlias(config, { adapter, from, to })` from `../shared/config`. See `axiom.ts` and `better-stack.ts`.
-- **Edge safety**: no `Buffer` (use `TextEncoder` + `btoa` for Basic auth — see `toBasicCredentials` in `loki.ts`), no Node-only imports. If a runtime genuinely can't be supported, return `null` from `resolve()` with a one-time warning (see `isEdgeRuntime()` in `fs.ts`).
+- **Edge safety**: no `Buffer` (use `TextEncoder` + `btoa` for Basic auth, see `toBasicCredentials` in `loki.ts`), no Node-only imports. If a runtime genuinely can't be supported, return `null` from `resolve()` with a one-time warning (see `isEdgeRuntime()` in `fs.ts`).

.agents/skills/create-adapter/references/test-template.md

@@ -6,10 +6,10 @@ Replace `{Name}`, `{name}`, `{NAME}` with the actual service name.
 
 Rules from the test README that apply here:
 
-- Use `mockFetch()` + `getFetchCall` / `getFetchJson` / `getFetchHeaders` from `../helpers/fetch` — don't hand-roll fetch spies in adapter tests (a few older files still do; follow the helpers, not them).
-- Delete every env var the adapter reads in `afterEach` — leaked env vars make later tests order-dependent.
-- Test exported pure helpers (`to{Name}Event`, `build{Name}Payload`, URL resolvers) in their own `describe` blocks — but only the ones the adapter actually exports. If the adapter has no converter (service accepts arbitrary JSON), drop the `to{Name}Event` import and its `describe` block entirely.
-- No `!` non-null assertions — use `defined()` from `../helpers/defined` if narrowing is needed.
+- Use `mockFetch()` + `getFetchCall` / `getFetchJson` / `getFetchHeaders` from `../helpers/fetch`, don't hand-roll fetch spies in adapter tests (a few older files still do; follow the helpers, not them).
+- Delete every env var the adapter reads in `afterEach`. Leaked env vars make later tests order-dependent.
+- Test exported pure helpers (`to{Name}Event`, `build{Name}Payload`, URL resolvers) in their own `describe` blocks, but only the ones the adapter actually exports. If the adapter has no converter (service accepts arbitrary JSON), drop the `to{Name}Event` import and its `describe` block entirely.
+- No `!` non-null assertions, use `defined()` from `../helpers/defined` if narrowing is needed.
 - Register the adapter in `encode-parity.test.ts` so the drain and `sendBatchTo{Name}` are pinned to the same encoder (not every existing adapter is registered there yet; new ones should be).
 
 ```typescript
@@ -160,9 +160,9 @@ describe('{name} adapter', () => {
 
 - **URL assertions**: Update expected URLs to the actual service API, including the path-already-present case if the encoder tolerates it (see `resolveLokiPushUrl`).
 - **Auth headers**: Match the service (`X-API-Key`, HTTP Basic, `X-ClickHouse-User`, …).
-- **Body format**: Wrapper objects (PostHog `{ api_key, batch }`), raw arrays (Axiom), NDJSON (ClickHouse) — assert the real structure, not just "is an array".
+- **Body format**: Wrapper objects (PostHog `{ api_key, batch }`), raw arrays (Axiom), NDJSON (ClickHouse). Assert the real structure, not just "is an array".
 - **Deprecated aliases**: If the adapter supports one (`token` → `apiKey`), add a test that the alias still resolves and that the canonical name wins when both are set.
-- **Error swallowing**: The drain itself never throws — that contract lives in `defineHttpDrain` and is covered by `test/toolkit/toolkit.test.ts`; don't re-test it per adapter. Only direct helpers surface errors.
+- **Error swallowing**: The drain itself never throws. That contract lives in `defineHttpDrain` and is covered by `test/toolkit/toolkit.test.ts`; don't re-test it per adapter. Only direct helpers surface errors.
 - **Service-specific helpers**: Every exported helper (`buildLokiPayload`, `toClickHouseRow`, severity mappers…) gets its own `describe` with edge cases (empty input, malformed timestamps, cardinality guards).
 
 ## Beyond unit tests

.agents/skills/create-enricher/SKILL.md

@@ -57,9 +57,9 @@ The contract is `defineEnricher<T>({ name, field, compute }, options?)`. You onl
 
 Key rules:
 
-- **Use the toolkit helpers**: `getHeader()` for case-insensitive header lookup, `normalizeNumber()` for numeric strings — both from `../shared/headers` (re-exported by `evlog/toolkit`).
-- **Single event field**: each enricher writes one top-level field on `ctx.event`. If the enricher must additionally pin top-level fields (like `createTraceContextEnricher` does for `event.traceId` / `event.spanId`), wrap the `defineEnricher` result in a closure — see that enricher for the pattern.
-- **Factory pattern**: `create{Name}Enricher(options: EnricherOptions = {})` returns the result of `defineEnricher(...)` — directly in the normal case, or through the thin closure wrapper when the enricher also pins top-level fields (see the single-event-field rule above).
+- **Use the toolkit helpers**: `getHeader()` for case-insensitive header lookup, `normalizeNumber()` for numeric strings. Both from `../shared/headers` (re-exported by `evlog/toolkit`).
+- **Single event field**: each enricher writes one top-level field on `ctx.event`. If the enricher must additionally pin top-level fields (like `createTraceContextEnricher` does for `event.traceId` / `event.spanId`), wrap the `defineEnricher` result in a closure, see that enricher for the pattern.
+- **Factory pattern**: `create{Name}Enricher(options: EnricherOptions = {})` returns the result of `defineEnricher(...)`, directly in the normal case, or through the thin closure wrapper when the enricher also pins top-level fields (see the single-event-field rule above).
 - **No side effects**: never throw, never log; rely on `defineEnricher`'s built-in error handling if something goes wrong.
 - **Export the Info type**: `{Name}Info` describing the field shape, exported alongside the factory.
 
@@ -69,12 +69,12 @@ Add tests to `packages/evlog/test/toolkit/enrichers.test.ts`, following the exis
 
 Required test categories:
 
-1. **Sets field from headers** — verify the enricher populates the event field correctly
-2. **Skips when source data missing** — verify no field is set when the required header/input is absent
-3. **Preserves existing data** — verify `overwrite: false` (default) doesn't replace user-provided fields
-4. **Overwrites when requested** — verify `overwrite: true` replaces existing fields
-5. **Handles edge cases** — empty strings, malformed values, case-insensitive header names
-6. **Default composition** — if the enricher joined `createDefaultEnrichers()`, extend that composition's tests
+1. **Sets field from headers**: verify the enricher populates the event field correctly
+2. **Skips when source data missing**: verify no field is set when the required header/input is absent
+3. **Preserves existing data**: verify `overwrite: false` (default) doesn't replace user-provided fields
+4. **Overwrites when requested**: verify `overwrite: true` replaces existing fields
+5. **Handles edge cases**: empty strings, malformed values, case-insensitive header names
+6. **Default composition**: if the enricher joined `createDefaultEnrichers()`, extend that composition's tests
 
 ## Step 3: Update the Enrichers Docs Page
 

.agents/skills/create-enricher/references/enricher-template.md

@@ -47,13 +47,13 @@ export function create{Name}Enricher(options: EnricherOptions = {}): (ctx: Enric
 ## Architecture Rules
 
 1. **Use the toolkit primitive**: `defineEnricher<T>({ name, field, compute }, options)` from `../shared/enricher` (re-exported as `evlog/toolkit`).
-2. **Use the toolkit helpers**: `getHeader()` for case-insensitive header lookup and `normalizeNumber()` for numeric strings — both from `../shared/headers`.
-3. **Single event field** — each enricher writes one top-level field on `ctx.event` (declared via the `field` option).
-4. **Return `undefined` to skip** — `compute` returning `undefined` makes the enricher a no-op for that event (no field merge, no errors).
-5. **Factory pattern** — always wrap `defineEnricher` in a `create{Name}Enricher(options?)` factory and return its result (directly, or through the closure wrapper of rule 7 when pinning top-level fields).
-6. **No try/catch** — `defineEnricher` already isolates errors (logs as `[evlog/{name}] enrich failed:` and never throws to the pipeline).
-7. **No mutation outside `compute`** — let `defineEnricher` handle the merge via `mergeEventField`. The one sanctioned exception: pinning top-level fields in addition to the enricher's own field, done by wrapping the `defineEnricher` result in a closure (see `createTraceContextEnricher`, which also sets `event.traceId` / `event.spanId`).
-8. **Composition** — to combine several enrichers into one callback, use `composeEnrichers` from `../shared/compose` (that's how `createDefaultEnrichers()` is built) instead of a manual loop.
+2. **Use the toolkit helpers**: `getHeader()` for case-insensitive header lookup and `normalizeNumber()` for numeric strings. Both come from `../shared/headers`.
+3. **Single event field**: each enricher writes one top-level field on `ctx.event` (declared via the `field` option).
+4. **Return `undefined` to skip**: `compute` returning `undefined` makes the enricher a no-op for that event (no field merge, no errors).
+5. **Factory pattern**: always wrap `defineEnricher` in a `create{Name}Enricher(options?)` factory and return its result (directly, or through the closure wrapper of rule 7 when pinning top-level fields).
+6. **No try/catch**: `defineEnricher` already isolates errors (logs as `[evlog/{name}] enrich failed:` and never throws to the pipeline).
+7. **No mutation outside `compute`**: let `defineEnricher` handle the merge via `mergeEventField`. The one sanctioned exception: pinning top-level fields in addition to the enricher's own field, done by wrapping the `defineEnricher` result in a closure (see `createTraceContextEnricher`, which also sets `event.traceId` / `event.spanId`).
+8. **Composition**: to combine several enrichers into one callback, use `composeEnrichers` from `../shared/compose` (that's how `createDefaultEnrichers()` is built) instead of a manual loop.
 
 ## Available Helpers