fix(baggage): do not percent-encode W3C baggage metadata

[arimu1]

Description

Fixes #6771.

The W3C Baggage propagator was percent-encoding and percent-decoding metadata (W3C properties) on inject/extract. That is not required by either the W3C Baggage spec or the OTel baggage API (metadata is an opaque string). Encoding breaks property key-value shape for other implementations after an extract→inject round-trip, e.g.:

SomeKey=SomeValue;ValueProp \t = \t PropVal
→ SomeKey=SomeValue;ValueProp%20%09%20%3D%20%09%20PropVal

Change: leave metadata untouched on inject and extract. Baggage entry values continue to be percent-encoded/decoded as before (aligned with the W3C requirement for list-member values).

This matches the approach used by opentelemetry-js (opaque pass-through).

Testing

• Updated W3CBaggagePropagatorTest.inject expectation (metadata not encoded)
• Added regression tests for W3C Baggage Propagator should not percent-encode metadata #6771:
  • inject_doesNotPercentEncodeMetadata
  • extract_metadataNotPercentDecoded
  • roundTrip_metadataPreservedOpaque
• Invalid percent sequences in metadata no longer drop the member (only invalid value encoding does)
• Fuzz tests: metadata generator excludes list separator , (safe without encoding)

Local:

./gradlew :api:all:test \
  --tests 'io.opentelemetry.api.baggage.propagation.W3CBaggagePropagatorTest' \
  --tests 'io.opentelemetry.api.baggage.propagation.W3CBaggagePropagatorFuzzTest' \
  --tests 'io.opentelemetry.api.baggage.propagation.BaggageCodecTest'

All green on Temurin 21.0.12 (macOS aarch64).

Compatibility note

This is a deliberate behavior change for interop with W3C-compliant / JS implementations. Callers that relied on Java-side percent-encoding of metadata will see raw metadata strings on the wire and on extract. Values are unchanged.

CNCF CLA: may need human sign-off if the CLA bot requests it.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: arimu1 / name: arimu1 (fb8a048)

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-08-06 04:19 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 91.62%. Comparing base (f8bd413) to head (3a146dd).
⚠️ Report is 10 commits behind head on main.

Files with missing lines	Patch %	Lines
.../api/baggage/propagation/W3CBaggagePropagator.java	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #8682      +/-   ##
============================================
+ Coverage     91.48%   91.62%   +0.13%     
+ Complexity    10467    10327     -140     
============================================
  Files          1021     1003      -18     
  Lines         27694    27137     -557     
  Branches       3247     3188      -59     
============================================
- Hits          25337    24864     -473     
+ Misses         1615     1566      -49     
+ Partials        742      707      -35     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jack-berg]

Curios if @SergeyKanzhelev or @basti1302 can confirm my understanding based on your involvement in w3c/baggage#145

[arimu1]

Thanks @jack-berg — addressed both threads:

1. Opaque metadata permalinks (OTel Set Value + Propagation) → reply on discussion_r3723923322
2. W3C property-value encoding (bbaf396 / Remove type from the resource. #145): encoding applies to list-member values and property values, not the whole OTel metadata blob → reply on discussion_r3723948657

Comment-only follow-up: 3a146dddb (no behavior change). Logic remains opaque pass-through for metadata; entry values still percent-encoded/decoded.

@SergeyKanzhelev @basti1302 — would appreciate a confirmation that this matches the #145 / #148 intent given OTel’s opaque metadata model.