wiki: audit fixes — broken links, wikilinks, frontmatter, stale content (66 files)

- Fixed 4 broken markdown links (bad relative paths in See Also sections)
- Corrected n8n port binding to 127.0.0.1:5678 (matches actual deployment)
- Updated SnapRAID article with actual majorhome paths (/majorRAID, disk1-3)
- Converted 67 Obsidian wikilinks to relative markdown links or plain text
- Added YAML frontmatter to 35 articles missing it entirely
- Completed frontmatter on 8 articles with missing fields

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

05-troubleshooting/security/clamscan-cpu-spike-nice-ionice.md

@@ -1,3 +1,12 @@
+---
+title: "ClamAV Safe Scheduling on Live Servers"
+domain: troubleshooting
+category: security
+tags: [clamav, cpu, nice, ionice, cron, vps]
+status: published
+created: 2026-04-02
+updated: 2026-04-02
+---
 # ClamAV Safe Scheduling on Live Servers
 
 Running `clamscan` unthrottled on a live server will peg CPU until completion. On a small VPS (1 vCPU), a full recursive scan can sustain 70–100% CPU for an hour or more, degrading or taking down hosted services.
@@ -70,4 +79,4 @@ kill <PID>
 ## Related
 
 - [ClamAV Documentation](https://docs.clamav.net/)
-- [[02-selfhosting/security/linux-server-hardening-checklist|Linux Server Hardening Checklist]]
+- [Linux Server Hardening Checklist](../../02-selfhosting/security/linux-server-hardening-checklist.md)