C4 fix: parity fixtures carry a recordKey with every Uri.EscapeDataString special character

A fourth fixture (escape) has a chunk recordKey of k!'()* <e-acute>%41+~. The provider's honest mount answers that one key as the canonical key
after logging the raw URL, so both consumers fetch the bytes and the log holds what each actually sent. The orchestrator asserts the C# and TS
URLs are identical and equal the RFC 3986 escaping. Deleting the reader's !'() * escape now fails test:interop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-10-19 20:45:35 +02:00
commit 11218b8889
4 changed files with 29 additions and 7 deletions

View file

@ -15,6 +15,7 @@ const cases: Record<string, () => Promise<Uint8Array>> = {
"honest-multi": () => fetchVerifiedContent(endpoints.honest, manifest("multi")),
"honest-single": () => fetchVerifiedContent(endpoints.honest, single),
"honest-empty": () => fetchVerifiedContent(endpoints.honest, manifest("empty")),
"honest-escape": () => fetchVerifiedContent(endpoints.honest, manifest("escape")),
"honest-single-chunk": () => fetchVerifiedChunk(endpoints.honest, single.chunks[0]!.chunkHash!, single.chunks[0]!.sizeBytes),
"tampered-multi": () => fetchVerifiedContent(endpoints.tampered, manifest("multi")),
"corrupt-single": () => fetchVerifiedContent(endpoints.corrupt, single),