fix(deployment): only block files with explicit confidential markers, not filename patterns

- Removed filename pattern checks (session-handoff, draft, etc.)
- Now only blocks files with content markers: [INTERNAL], [CONFIDENTIAL], [DO NOT PUBLISH]
- Allows session handoff and internal documentation in docs/ directory
- Still blocks actual credentials and sensitive content

Rationale: Filename patterns were too broad and blocked legitimate internal documentation.
Session handoffs are fine in docs/ as long as they don't contain actual sensitive data.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
TheFlow 2025-10-26 23:19:18 +13:00
parent 3aae86edf9
commit 8021197bf0

View file

@ -81,19 +81,17 @@ function scanFile(filePath) {
if (!['.md', '.txt', '.pdf', '.doc', '.docx', '.html'].includes(ext)) {
return null;
}
// Check filename
const pathCheck = checkFilePath(filePath);
if (pathCheck.confidential) {
return { file: filePath, ...pathCheck };
}
// Check content
// ONLY check content markers, not filename patterns
// Rationale: Session handoffs and internal docs are fine in docs/ directory
// as long as they don't contain actual sensitive content (credentials, etc.)
// Filename patterns are too broad and catch legitimate internal documentation
const contentCheck = checkFileContent(filePath);
if (contentCheck.confidential) {
return { file: filePath, ...contentCheck };
}
return null;
}