docs: reflect the operation-tracing stage in CLAUDE.md

CLAUDE.md's pipeline overview listed the shipped policies and the default
stack order without the new operation-tracing stage that brackets the
redirect/retry wrappers.

- Add operation-tracing to the shipped-policies list and note it ships
  sync-only alongside logging and tracing.
- Put operation-tracing at the head of the documented default stack order.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: OmarAlJarrah

CLAUDE.md

@@ -206,15 +206,16 @@ Layered, bottom-up:
 4. **`pipeline`** — `Policy` (and `AsyncPolicy`) wrap the downstream chain;
    `Pipeline` / `AsyncPipeline` run an ordered set of policies grouped into
    `Stage`s via `StagedPipelineBuilder`. Shipped policies: redirect,
-   idempotency, retry, set-date, client-identity, logging, tracing. Async
-   twins under `pipeline/policies/` exist only for redirect, idempotency,
-   retry, set-date, and client-identity; logging and tracing are sync-only.
+   idempotency, retry, set-date, client-identity, logging, tracing, and
+   operation-tracing. Async twins under `pipeline/policies/` exist only for
+   redirect, idempotency, retry, set-date, and client-identity; logging,
+   tracing, and operation-tracing are sync-only.
    `default_pipeline()` / `default_async_pipeline()` assemble the standard
-   stack in the order redirect → idempotency → retry → set-date →
-   client-identity → [auth] → logging → tracing (the async pipeline omits
-   logging and tracing). The lower-level `pipeline/step/PipelineStep` Protocol
-   (`(input, context) -> output`) plus `StepMetadata` remain for custom
-   composition.
+   stack in the order operation-tracing → redirect → idempotency → retry →
+   set-date → client-identity → [auth] → logging → tracing (the async
+   pipeline omits the tracing and logging policies). The lower-level
+   `pipeline/step/PipelineStep` Protocol (`(input, context) -> output`) plus
+   `StepMetadata` remain for custom composition.
 5. **`client/HttpClient`** — single-method Protocol
    (`execute(request) -> Response`). Transport is **not** provided by `core`;
    the `dexpace-sdk-http-*` packages (stdlib, httpx, aiohttp, requests) each