windyboy
a3ee8c09cf
- replace real keys/passwords/tokens/connection strings with {{SECRET_*}}
placeholders across 24 files (review-named 12 + noise-audit finds:
WAQI/Dovecot/GPS/VPN subscriptions/Work runbooks/Plane API key)
- widen verifier: OPENSSH/RSA key headers, hyphenated sk-/prefixed sk-,
credential assignments & table cells, telegram bot tokens, conn strings
- placeholder/default-value/config-name exemptions to kill doc FPs
- skip .obsidian plugin code and frozen Inbox-Clippings from value scan
- GIT_WORKFLOW: no git add ., verifier before commit, force-push exception
- final regression: 0 flagged in tracked scope (was 43)
Archive
Purpose: Completed or inactive items from Projects and Areas.
What Gets Archived
- Completed projects - Move entire project folder here
- Inactive areas - Areas you're no longer maintaining
- Old resources - Outdated reference materials (use sparingly)
Archive Structure
Maintain the same folder structure:
Projects/- Completed project foldersAreas/- Inactive areasResources/- Outdated resources (if needed)
Before Archiving a Project
- Create a project summary note with:
- What was accomplished
- Key learnings
- Links to important outputs
- Update related Area notes
- Move the entire project folder here
Maintenance
- Review quarterly to see what can be deleted
- Some archived items may be reactivated
- Keep the archive organized (mirror active structure)
Tips
- Don't archive too aggressively - keep valuable reference material
- Use git history to track when things were archived
- Archived doesn't mean forgotten - you can still search and reference