Avoid logging captured environment values

[shunichironomura]

Warning

This content was written by an AI agent and must be verified by a human developer. After human verification, this alert may be removed.

Summary

• stop including captured environment-variable values in capture-env debug logs
• retain the variable name and byte length for diagnostics
• address only the logging portion of capture-env logs captured values in plaintext and stores them unredacted #1083

Raw values are still persisted in capture output. Redaction/hash-only capture mode is intentionally deferred.

AI assistance

• AI used: yes — Amp investigated the issue, implemented the change, and ran verification
• Human review of AI-assisted code: pending

Breaking changes

• No breaking changes
• Breaking changes; the breaking change label is applied

Verification

• cargo test -p capsula-capture-env
• cargo fmt --check --all
• cargo clippy -p capsula-capture-env --all-targets --all-features -- -D warnings
• end-to-end CLI run with debug logging, asserting the test secret was absent while the variable name and byte length were present

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.16%. Comparing base (433b438) to head (7d4ea91).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1226   +/-   ##
=======================================
  Coverage   54.16%   54.16%           
=======================================
  Files          44       44           
  Lines        4233     4233           
=======================================
  Hits         2293     2293           
  Misses       1940     1940           

☔ 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.