Two distinct atomicity guarantees, not one:
fs.writeFile is independent. A real I/O failure partway
through (disk full, permissions changed mid-run) can leave some
artifacts on disk and not others. Transactional (temp-file + rename)
writes across all three artifacts were considered and rejected as
disproportionate machinery for a rare failure mode -- see ADR 0011.
Orchestrates generateEnvManifest/generateDocumentation/ generateUsageReport, plus the persisted evidence artifact, by composing their shared private compute/write pipeline directly, running schema discovery+linking exactly once regardless of how many outputs are requested -- an orchestrator, not a new analysis engine (see ADR 0011).