Fix secret redaction test expectations for full redaction format

[Copilot]

A test case in redact_secrets.test.cjs was failing because it expected partial redaction (abc***) while the implementation correctly uses full redaction (***REDACTED***).

Changes

• Updated test assertion in "should redact 6-character secrets" case to expect ***REDACTED*** instead of abc***
• Aligns test expectations with the CWE-200 security fix that prevents information disclosure through prefix preservation

// Before (incorrect expectation)
expect(fs.readFileSync(testFile, "utf8")).toBe("Secret: abc*** test"));

// After (matches secure implementation)
expect(fs.readFileSync(testFile, "utf8")).toBe("Secret: ***REDACTED*** test"));

The implementation in redact_secrets.cjs was already correct—this only updates the test to match.

Original prompt

Fix ci failures

Custom agent used: ci-cleaner
Tidies up the repository CI state by formatting sources, running linters, fixing issues, running tests, and recompiling workflows

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes a failing unit test by aligning the expected redaction output with the existing secure redaction behavior (full replacement with a fixed string to avoid prefix disclosure).

Changes:

• Update the "should redact 6-character secrets" test assertion to expect full redaction (***REDACTED***) instead of partial masking.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.