feat: Add --redact-body-fields option to prevent credentials in tapes

[NikoRoberts]

Summary

Add --redact-body-fields CLI option to redact sensitive JSON fields in request and response bodies during tape recording. This prevents credentials like passwords, tokens, and API keys from being written to disk.

What was done

Implemented body field redaction in Proxay core:

1. CLI Option

proxay --mode record --host https://api.example.com \
  --tapes-dir ./tapes \
  --redact-body-fields password,access_token,refresh_token,api_key

2. Implementation Details

• Location: src/persistence.ts (redaction before serialization)
• Parsing: UTF8-encoded JSON bodies only (binary/non-JSON unchanged)
• Matching: Case-insensitive field names
• Recursion: Handles nested objects and arrays
• Redaction value: XXXX (matches existing --redact-headers pattern)

3. Example

Before redaction:

{"email": "[email protected]", "password": "secret123"}

After redaction:

{"email": "[email protected]", "password": "XXXX"}

Changes

Core Files

• src/cli.ts - Added --redact-body-fields option
• src/server.ts - Wired option to Persistence layer
• src/persistence.ts - Implemented redaction logic
  • redactBodyFields() - Main entry point
  • redactBufferFields() - JSON parsing and Buffer conversion
  • redactObjectFields() - Recursive field redaction

Tests Added (9 comprehensive tests)

• ✅ Redacts simple JSON fields
• ✅ Case-insensitive matching
• ✅ Nested object redaction
• ✅ Array handling
• ✅ Response body redaction
• ✅ Non-JSON body handling (returns unchanged)
• ✅ Binary body handling (returns unchanged)
• ✅ Empty body handling
• ✅ No-op when no fields specified

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[timdawborn]

LGTM apart from the linting issues.