# Changelog

## Score

- CAI 70 → 71 (+0.9)

## Lenses

- Code Health 95 → 95 (+0.0)
- Architecture 99 → 99 (+0.0)
- Maturity 64 → 66 (+1.9)
- Readiness 71 → 71 (+0.0)
- Security 71 → 71 (+0.0)
- Performance 85 → 85 (+0.0)

## Resolved (10)

- Ambiguous 'new' naming. `Dispatch::new` creates a Dispatch from a Subscriber. `Subscriber::new_span` creates a Span ID. `Dispatch::new_span` also creates a Span ID. The method name `new_span` on `Dispatch` is confusing because it doesn't 'create' a Span object in the user-facing sense, but rather a Span ID handle, and it delegates to the subscriber. It overlaps in intent with `Subscriber::new_span` but is exposed on the Dispatch layer.
- Documentation: no project overview (tracing/README.md)
- Duplicate struct definition. The `Instrumented` struct is defined in both `tracing::instrument` and `tracing_futures`. While they have the same core accessors, `tracing_futures::Instrumented` adds future-specific methods (`spawn`, `block_on`). This creates two distinct types with the same name in different namespaces that share a significant portion of their API, confusing users about which type to use for general instrumentation vs. future instrumentation.
- Duplicate trait definitions across modules. The `Instrument` trait is defined in both `tracing::instrument` and `tracing_futures` with identical signatures. Similarly, `WithSubscriber` is duplicated in both modules. This forces users to import from specific crates depending on whether they are instrumenting standard types or futures, creating API fragmentation.
- Inconsistent naming convention for explicit dispatch parameters. The API uses `_with` suffix for constructors that accept a `Dispatch` (e.g., `new_with`, `child_of_with`, `new_root_with`). However, other methods like `enter`, `record`, `follows_from` do not have `_with` variants for explicit dispatch, implying they use the current global/default dispatch. While this is a design choice, the inconsistency between 'implicit dispatch' methods and 'explicit dispatch' methods (named with `_with`) is a minor stylistic inconsistency, but more importantly, `Span::new` vs `Span::new_with` creates a parallel constructor pattern that is not mirrored in other span lifecycle methods like `enter` or `record`.
- Most significant orphaned file (tracing-core/src/subscriber.rs)
- Most significant orphaned file (tracing-mock/src/span.rs)
- Most significant orphaned file (tracing-subscriber/src/fmt/format/json.rs)
- Off-boarding risk: anonymized user #1
- Workflow token permissions not restricted

## New (65)

- Most significant orphaned file (tracing-subscriber/src/fmt/fmt_layer.rs)
- Most significant orphaned file (tracing-subscriber/src/layer/mod.rs)
- Most significant orphaned file (tracing/src/span.rs)
- Off-boarding risk: anonymized user #1
- Orphaned file (tracing-appender/src/non_blocking.rs)
- Orphaned file (tracing-appender/src/rolling/builder.rs)
- Orphaned file (tracing-appender/src/worker.rs)
- Orphaned file (tracing-core/src/callsite.rs)
- Orphaned file (tracing-core/src/dispatcher.rs)
- Orphaned file (tracing-core/src/event.rs)
- Orphaned file (tracing-core/src/field.rs)
- Orphaned file (tracing-core/src/span.rs)
- Orphaned file (tracing-core/src/spin/mutex.rs)
- Orphaned file (tracing-core/src/spin/once.rs)
- Orphaned file (tracing-core/src/subscriber.rs)
- Orphaned file (tracing-error/src/error.rs)
- Orphaned file (tracing-error/src/layer.rs)
- Orphaned file (tracing-futures/src/executor/futures_01.rs)
- Orphaned file (tracing-futures/src/executor/futures_03.rs)
- Orphaned file (tracing-journald/src/socket.rs)
- …and 45 more
