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

    Interface CompatibilityIssue

    One compatibility problem found between two or more declarations of the same variable, or an exclusive-group violation.

    interface CompatibilityIssue {
        code?: CompatibilityIssueCode;
        files: readonly string[];
        reason: string;
        severity: "warning" | "error" | "info";
        variable: string;
    }
    Index

    Stable, machine-readable identifier for CI filtering / doc-linking / GitHub Action annotations / IDE integration. undefined only for checks that don't (yet) set one -- see CompatibilityIssueCode for the full enumerated list of values a check in this file can produce.

    files: readonly string[]

    Every file declaring a conflicting definition. A pairwise comparison (compatibility.ts, exclusive-group.ts) always produces exactly two; a finding escalated from another family (generate-env-artifacts.ts's escalatedFindings(), via findingFiles()) can produce zero, one, or two, depending on what location information that finding actually carries -- genuinely variable arity, not a tuple.

    reason: string

    Human-readable explanation of the conflict.

    severity: "warning" | "error" | "info"

    "error" blocks generation regardless of onIncompatibility; "warning" blocks only when onIncompatibility: "throw"; "info" never blocks, under any flag.

    variable: string

    The environment variable name, or "(contract) <name>" for a contract-level (e.g. exclusive-group) issue.