Add redact.ts regression tests for nested errors and Stellar seed false-positives

[mikewheeleer]

Description

Strengthen src/redact.test.ts to assert secrets are redacted within deeply nested objects, arrays, and Error stack traces, while public Stellar keys and contract IDs are NOT over-redacted.

Requirements and context

• Cover nested/array/Error-stack redaction and round-trip through the pino logger.
• Assert no false positives on Stellar public keys (G...) and contractMetadata IDs.
• Acceptance: deterministic tests; coverage on redact.ts >= 95%; explicit cases for each secret pattern.

Suggested execution

• Fork the repo and create a branch:
  • git checkout -b test/redact-regression
• Implement changes:
  • src/redact.ts
  • Tests: src/redact.test.ts
  • Docs: docs/backend
  • Include TSDoc/NatSpec-style doc comments
  • Validate security assumptions (input validation, auth, signature verification, secret redaction, idempotency)

Test and commit

• Run tests: npm test (coverage: npm run test:ci)
• Cover edge cases
• Include test output and security notes in the PR

Example commit message

test(security): expand redaction regression coverage

Guidelines

• Minimum 95% line coverage on new/changed code
• No secrets in repo; use .env + deployment secrets only
• Clear documentation
• Timeframe: 96 hours from assignment

[deborahamoni0-prog]

@deborahamoni0-prog has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hey! I'd like to take this on.
I'll strengthen src/redact.test.ts with deterministic test cases covering nested object redaction, array redaction, Error stack trace redaction, and round-trip through the pino logger — while explicitly asserting no false positives on Stellar public keys (G...) and contractMetadata IDs. I'll add TSDoc comments to src/redact.ts, document security assumptions in docs/backend, and ensure coverage on redact.ts hits ≥ 95%.
Ready to start immediately. Can this be assigned to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @deborahamoni0-prog to this issue.

[drips-wave]

Congratulations, @deborahamoni0-prog! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @deborahamoni0-prog: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊