docs(traces): apply and archive the traces capability spec

README.md

@@ -21,6 +21,7 @@ Tags on each feature indicate whether scenarios apply to client SDKs, server SDK
 | Capability | Spec | Scope | Status |
 |------------|------|-------|--------|
 | Logs | [`openspec/specs/logs/spec.md`](openspec/specs/logs/spec.md) | product | Canonical |
+| Traces | [`openspec/specs/traces/spec.md`](openspec/specs/traces/spec.md) | product | Canonical |
 | Tracing Headers | [`openspec/specs/tracing-headers/spec.md`](openspec/specs/tracing-headers/spec.md) | cross-SDK correlation | Canonical |
 | Alias | [`openspec/specs/alias/spec.md`](openspec/specs/alias/spec.md) | public API | Canonical |
 | Capture | [`openspec/specs/capture/spec.md`](openspec/specs/capture/spec.md) | public API | Canonical |

openspec/changes/add-traces/tasks.md → openspec/changes/archive/2026-07-31-add-traces/tasks.md

@@ -35,19 +35,19 @@
 
 ## 3. Prose alignment (applied at archive, outside the requirement-delta mechanism)
 
-- [ ] 3.1 Add a Purpose section to `openspec/specs/traces/spec.md` (logs-style, 2-3
+- [x] 3.1 Add a Purpose section to `openspec/specs/traces/spec.md` (logs-style, 2-3
   paragraphs): traces as a separate pipeline (own queue, `/i/v1/traces`, own flush), distinct
   from `tracing-headers` and LLM analytics, plus derivation provenance ("derived from the
   Rust `capture-logs` ingestion service, verified empirically against production 2026-07-20,
   and the logs pipeline as template — spec precedes the first SDK implementation")
-- [ ] 3.2 Add the traces pipeline to the Capabilities list in `openspec/project.md`
-- [ ] 3.3 Add a Traces row to the Capabilities table in the top-level `README.md`
+- [x] 3.2 Add the traces pipeline to the Capabilities list in `openspec/project.md`
+- [x] 3.3 Add a Traces row to the Capabilities table in the top-level `README.md`
   (`product` scope, like Logs)
 
 ## 4. Validation
 
 - [x] 4.1 Run `openspec validate --strict` and resolve any errors (passing as of 2026-07-21)
-- [ ] 4.2 Run `/opsx:apply` then `/opsx:archive` to create `specs/traces/spec.md`
+- [x] 4.2 Run `/opsx:apply` then `/opsx:archive` to create `specs/traces/spec.md`
 
 ## 5. Downstream follow-up (separate changes, not this one)
 

openspec/project.md

@@ -24,7 +24,8 @@ Specs now cover three groups of canonical SDK behavior:
   persistent storage, remote config, feature-flag caches/evaluators, session management, surveys,
   consent gating, replay privacy, and client/server tracing-header correlation.
 - **Product pipelines** such as logs, whose records are enriched, batched, and shipped as
-  OpenTelemetry Logs (OTLP/HTTP JSON) at `POST {host}/i/v1/logs`.
+  OpenTelemetry Logs (OTLP/HTTP JSON) at `POST {host}/i/v1/logs`, and traces, whose spans are
+  shipped as OpenTelemetry Traces (OTLP/HTTP JSON) at `POST {host}/i/v1/traces`.
 
 Add a new sibling under `specs/<capability>/` for each genuinely distinct capability. One
 capability per folder.