tga 2.16.0

//! AUDIT mode — the one-shot, full-dataset sweep behind `tga audit` (DOC-67).
//!
//! Why: acquisition due diligence points one command at an org and reads the
//! result once, under time pressure. DOC-67 §2 makes that literal — nothing in
//! this module prompts, waits for input, or needs a terminal.
//! What: [`run_full_sweep`], the library entry point that drives tga's eight
//! data-collection subcommands end to end, plus the per-stage outcome types it
//! returns. The `tga audit` command (`crate::commands::audit`) owns
//! orchestration and reporting; this module owns stage sequencing and nothing
//! else.
//! Test: `audit::tests`.
//!
//! ## Stage order
//!
//! DOC-67 §5's prose lists the sweep as "collect → classify → report →
//! pr-metrics → jira → dora → deployments → incidents". That is the spec's
//! enumeration of which subcommands participate, not a runnable order: `dora`
//! reduces `fact_deployments` / `fact_incidents` (§8), so running it before the
//! two commands that populate those tables would compute the four DORA keys
//! over empty input, and `report` renders what the earlier stages produced, so
//! running it third would render a mostly empty report. The executed order is
//! therefore data-flow order — see [`SweepStage`].

mod gaps;
mod review;
mod stage;
mod sweep;

#[cfg(test)]
mod tests;

/// The excerpt cap, visible to `report::dd_manifest_tests` so its
/// boundary-straddle tests position a credential against the real value instead
/// of a copy that can drift away from it (#5308 review).
#[cfg(test)]
pub(crate) use gaps::MAX_REASON_CHARS;
pub use gaps::{sweep_gap_lines, DATA_HANDLING_NOTE};
pub use review::{
    artifact_paths, resolve_review_binary, run_review_report, ReviewRun, ReviewRunError,
    DEFAULT_REVIEW_BIN, ENV_REVIEW_BIN,
};
pub use stage::{AuditSweepStats, StageOutcome, StageStatus, StaleFetch, SweepStage};
pub use sweep::{run_full_sweep, SweepOptions};