Staging before production
The active theme is not the default write target.
TaskerArmy is designed around a simple contract: inspect first, write to staging, show the evidence and require intentional production approval.
The active theme is not the default write target.
Changesets, QA output, AI review and preview provide multiple ways to inspect the work.
The merchant remains the authority over production. Drift checks reduce the risk of overwriting changes made outside TaskerArmy.
No software can guarantee zero risk. The product reduces preventable risk and makes uncertainty visible.
The dashboard can support a deliberate human override for false positives. The reason should be recorded and production permissions should remain restricted.
Rollback is a control, not magic. Changes made after deployment must be considered before reverting files.