1fc9fa0f5f
Add literate programming phase 1 documentation for: - logging.sh: transparency and auditability during operations - rollback.sh: cleanup strategy after failures Decision: Plain text logs for readability over structured JSON. Log destination is /tmp/void-wrapper-YYYY-MM-DD-HHMMSS.log to avoid conflicts in multi-run sessions. Logs remain ephemeral in live environment, not copied to target system. Decision: Three log levels (INFO, WARN, ERROR) with clear separation between stdout (user-facing) and log file (detailed trace). Secret masking prevents passphrase exposure. Decision: Best-effort rollback limited to reversible operations. Unmount filesystems and close LUKS mappings, but never revert partitioning or formatting (irreversible without data loss). Only cleanup after explicit user confirmation. Rationale: Full automatic rollback rejected due to complexity and risk. Partial cleanup with clear manual recovery instructions is safer and more transparent. Track failed phase to provide targeted recovery advice. Open questions for phase 2: - Support verbose/debug mode beyond standard levels? - Display log path at end for manual review? - Handle log rotation in multi-run sessions?