@maverickcer/env-cap
    Preparing search index...

    Function generateEnvArtifacts

    • 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).

      Parameters

      Returns Promise<GenerateEnvArtifactsResult>

      Two distinct atomicity guarantees, not one:

      • Compute atomicity (guaranteed): every requested pass's blocking findings are checked, across all passes, before any pass writes anything.
      • Write atomicity (NOT guaranteed, and not attempted): once writes begin, each 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.

      If any requested output location escapes root, or if any requested pass reports a blocking finding.