Maintainer backlog item
The migration audit records that sensitive-file scans were performed, but the public repository should have stronger test coverage for future changes.
Why this matters
WebMuse should prevent accidental public exposure of secrets, local machine paths, customer materials, recordings, extracted frames, and generated output.
Proposed scope
Add or expand tests for:
- fake API key patterns
- fake token patterns
- local Windows path examples
- generated artifact paths
- ignored customer/private material folders
- output-site runtime paths
Acceptance criteria
- Tests use fake sentinel strings only.
- No real credentials or private files are introduced.
- FoundationSelfTest or a dedicated test project covers the expected sanitizer behavior.
Maintainer backlog item
The migration audit records that sensitive-file scans were performed, but the public repository should have stronger test coverage for future changes.
Why this matters
WebMuse should prevent accidental public exposure of secrets, local machine paths, customer materials, recordings, extracted frames, and generated output.
Proposed scope
Add or expand tests for:
Acceptance criteria