Generate (or maintain a section of) `AGENTS.md` from the active rule set, so the agent's pre-prompt directives stay in sync with the lint config. Outputs to stdout by default; use `--output PATH` to write a file or `--inline --output PATH` to splice between `<!-- alint:start -->` / `<!-- alint:end -->` markers

Usage: alint[EXE] export-agents-md [OPTIONS]

Options:
  -c, --config <CONFIG>       Path to a config file (repeatable; later overrides earlier)
      --output <PATH>         Output destination. Without `--inline`, the file is overwritten. Omit for stdout
      --inline                Splice the generated section between `<!-- alint:start -->` and `<!-- alint:end -->` markers in `--output PATH`. Markers are auto- created (with a stderr warning) when the target file lacks them
      --no-gitignore          Disable .gitignore handling (overrides config)
      --section-title <TEXT>  Heading text for the generated section. Default: "Lint rules enforced by alint"
      --fail-on-warning       Treat warnings as errors for exit-code purposes
      --include-info          Include `level: info` rules. Default omits them — info-level rules are nudges, not directives
      --color <WHEN>          When to emit ANSI color codes in human output. `auto` (the default) inspects TTY + `NO_COLOR` + `CLICOLOR_FORCE`. Only affects the `human` format; `json` / `sarif` / `github` / `markdown` / `junit` / `gitlab` / `agent` are always plain bytes [default: auto] [possible values: auto, always, never]
  -f, --format <FORMAT>       Output format. `markdown` (default) is the canonical `AGENTS.md` shape; `json` is parallel to `suggest`'s JSON envelope for agent consumption [default: markdown] [possible values: markdown, json]
      --ascii                 Force ASCII glyphs in human output (e.g. `x` instead of `✗`). Auto-enabled when `TERM=dumb`
      --compact               Compact one-line-per-violation human output, suitable for piping into editors / grep / `wc -l`. Format: `path:line:col: level: rule-id: message`
      --progress <WHEN>       When to render progress on stderr for slow operations (currently `alint suggest`). `auto` (the default) renders when stderr is a TTY; `always` forces; `never` silences. Progress always lives on stderr — `--format` JSON / YAML output on stdout stays byte-clean [default: auto] [possible values: auto, always, never]
  -q, --quiet                 Suppress progress and any stderr summary lines. Alias for `--progress=never` plus suppression of the "found N proposals in Ts" footer that `suggest` prints
  -h, --help                  Print help
