v0.2.0

Changes since v0.1.0

Behavior-only improvements to the consumer/producer spans; the public API is unchanged (still a drop-in get_message_store_with_open_telemetry wrapper).

• Fix span-metric cardinality. Consumer spans are now named by the low-cardinality subscription subject + consumer (nats process {subject} ({consumer})); producer spans replace per-message id tokens (Mongo ObjectId / UUID) with {id}. The full subject stays on messaging.destination.name. This stops every message from minting its own traces_spanmetrics_* series.
• Rename the helper to replace_subject_ids_with_placeholder (says what it does).
• New per-trace consumer-span attributes (when present): messaging.message.body.metadata.originSubject, the first-class messaging.message.body.metadata.traceId (Python zen_log), and messaging.message.body.metadata.__zenlog.traceId (JS zen-log).
• Add span-exporter + helper unit tests (.[test] extra); wired into ci-dispatch pre-merge.

v0.1.0

Initial release