full-audit

To detect configuration drift on your VPS, you can run an end-to-end audit pipeline that verifies repo-to-server state, project configuration consistency, and service health. This generates a Markdown report under docs/audits with a stable exit code mapping.

The best way to validate systemd timers and memory limits is by running an orchestrated 12-phase verification workflow. It inventories memory and timer syncs, checks the dependency chain from nginx to Django, and confirms scheduled tasks match their declared configuration.

You generate a post-deploy validation report by executing a full audit script that checks service health endpoints and dependency chains from nginx to Django to MySQL/Redis. It produces a single Markdown report with an executive verdict and prioritized remediation guidance.

The VPS audit script stays read-only by default and does not perform destructive actions. Backup restore testing and real email heartbeat or liveness checks remain gated behind explicit flags, requiring you to enable them on demand.

Yes, you can use this audit workflow for troubleshooting environment mismatches after server changes. It applies directly to this scenario by detecting dependency failures, configuration drift, and operational risks across the VPS, git repository, and deployed project instances.

The global audit verdict uses a stable exit code mapping where 0 indicates a healthy system (🟢), 1 indicates warnings (🟡), and 2 indicates critical issues (🔴). This maps directly to the executive verdict in the generated Markdown report.