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>

02-selfhosting/security/ansible-unattended-upgrades-fleet.md

@@ -90,5 +90,5 @@ ansible-playbook update.yml -l dca,majorlinux,majortoot
 
 ## See Also
 
-- [[ansible-getting-started|Ansible Getting Started]]
-- [[linux-server-hardening-checklist|Linux Server Hardening Checklist]]
+- [Ansible Getting Started](../../01-linux/shell-scripting/ansible-getting-started.md)
+- [Linux Server Hardening Checklist](linux-server-hardening-checklist.md)

02-selfhosting/security/fail2ban-apache-404-scanner-jail.md

@@ -1,3 +1,12 @@
+---
+title: "Fail2ban Custom Jail: Apache 404 Scanner Detection"
+domain: selfhosting
+category: security
+tags: [fail2ban, apache, security, scanner, firewall]
+status: published
+created: 2026-04-02
+updated: 2026-04-02
+---
 # Fail2ban Custom Jail: Apache 404 Scanner Detection
 
 ## The Problem

02-selfhosting/security/linux-server-hardening-checklist.md

@@ -236,5 +236,5 @@ Reference: [sa-learn documentation](https://spamassassin.apache.org/full/3.0.x/d
 
 ## See Also
 
-- [[managing-linux-services-systemd-ansible]]
-- [[debugging-broken-docker-containers]]
+- [managing-linux-services-systemd-ansible](../../01-linux/process-management/managing-linux-services-systemd-ansible.md)
+- [debugging-broken-docker-containers](../docker/debugging-broken-docker-containers.md)

02-selfhosting/security/selinux-fail2ban-execmem-fix.md

@@ -1,3 +1,12 @@
+---
+title: "SELinux: Fixing Fail2ban grep execmem Denial on Fedora"
+domain: selfhosting
+category: security
+tags: [selinux, fail2ban, fedora, execmem, security]
+status: published
+created: 2026-04-02
+updated: 2026-04-02
+---
 # SELinux: Fixing Fail2ban grep execmem Denial on Fedora
 
 ## The Problem
@@ -82,5 +91,5 @@ Writing the `.te` file manually is more reliable and self-documenting.
 
 ## See Also
 
-- [Docker & Caddy Recovery After Reboot (Fedora + SELinux)](../../../05-troubleshooting/docker-caddy-selinux-post-reboot-recovery.md) — another SELinux fix for post-reboot service issues
-- [SELinux: Fixing Dovecot Mail Spool Context](../../../05-troubleshooting/selinux-dovecot-vmail-context.md) — custom SELinux context for mail spool
+- [Docker & Caddy Recovery After Reboot (Fedora + SELinux)](../../05-troubleshooting/docker-caddy-selinux-post-reboot-recovery.md) — another SELinux fix for post-reboot service issues
+- [SELinux: Fixing Dovecot Mail Spool Context](../../05-troubleshooting/selinux-dovecot-vmail-context.md) — custom SELinux context for mail spool

02-selfhosting/security/ufw-firewall-management.md

@@ -174,4 +174,4 @@ The Fedora servers (majorlab, majorhome, majormail, majordiscord) use iptables o
 ## See Also
 
 - [Linux Server Hardening Checklist](linux-server-hardening-checklist.md) — initial firewall setup as part of server provisioning
-- [Fail2ban & UFW Rule Bloat Cleanup](../../../05-troubleshooting/networking/fail2ban-ufw-rule-bloat-cleanup.md) — what happens when manual blocks get out of hand
+- [Fail2ban & UFW Rule Bloat Cleanup](../../05-troubleshooting/networking/fail2ban-ufw-rule-bloat-cleanup.md) — what happens when manual blocks get out of hand