feat: implement responsive mobile navigation header and wiki sidebar drawer

- Refactored templates/base.html to hide navigation on mobile and expose a hamburger menu button.
- Built a right-aligned sliding mobile menu drawer sheet in base.html.
- Hidden the documentation sidebar in templates/docs/sidebar.html by default on mobile, placing it inside a left-aligned sliding drawer sheet.
- Added a floating 'Explore Guides' directory trigger bar at the top of doc pages on mobile.
- Updated static/js/components.js to apply active route highlighting globally to both desktop and mobile sidebars.

templates/docs/logging.html

@@ -232,6 +232,24 @@ where
                         The `payload` field is crucial. By storing the JSON serialization of the model BEFORE or AFTER the action, system administrators can reconstruct state history. For deletions, always record the serial snapshot of the deleted model in the payload so it is never permanently lost to audit inquiries.
                     </p>
                 </div>
+
+                <div>
+                    <span class="font-bold text-indigo-400 block mb-1">🗑️ Compliance & Archival Purging</span>
+                    <p class="text-slate-400 leading-normal">
+                        To maintain storage hygiene, administrators can purge logs older than <code>x</code> days (minimum 1 day). To prevent accidental loss of audit history, the system enforces a strict <strong>archival download requirement</strong>:
+                    </p>
+                    <ul class="list-disc pl-5 mt-1.5 space-y-1.5 text-slate-400 leading-normal">
+                        <li>
+                            The purge action queries the records target for deletion and serializes them to JSON format in memory.
+                        </li>
+                        <li>
+                            The database records are deleted, and a new audit log entry recording the purge event details is created to preserve the audit trail chain.
+                        </li>
+                        <li>
+                            The server immediately streams the JSON data as a downloadable attachment, forcing the browser to save the backup locally.
+                        </li>
+                    </ul>
+                </div>
             </div>
         </section>