export declare const EXIT_CODES = "\nEXIT CODES:\n  0    Success (no validation errors)\n  1    Validation errors (orphans, broken links)\n  2    Usage errors (invalid arguments)\n  130  Interrupted (SIGINT, SIGTERM)\n";
export declare const ENVIRONMENT_VARS = "\nENVIRONMENT:\n  NO_COLOR\n      Disable colored output globally (respects no-color.org standard).\n      When set to any value, colors are disabled regardless of TTY detection.\n      Equivalent to --no-colors flag. Takes precedence over FORCE_COLOR.\n\n  FORCE_COLOR\n      Force colored output even when piped to other tools.\n      Useful for debugging or when piping to color-aware tools.\n      Equivalent to --colors flag. Overridden by NO_COLOR.\n\n  CI=true\n      Automatically disables colors in CI/CD environments.\n      Prevents color escape codes in build logs and CI output.\n      Can be overridden with FORCE_COLOR if needed.\n";
export declare const CONFIG_PRECEDENCE = "\nCONFIGURATION:\n  Config files loaded in priority order:\n    1. CLI flags (--entrypoint, --format, etc.)\n    2. Project config (.mditerc, mdite.config.js, package.json#mdite)\n    3. User config (~/.config/mdite/config.json)\n    4. Built-in defaults\n\n  See: mdite init --help\n       mdite config --help\n";
export declare const MAIN_DESCRIPTION = "\nDESCRIPTION:\n  mdite treats your markdown documentation as a connected system (graph),\n  not isolated files. This enables system-wide operations: validation,\n  dependency analysis, file listing, and content output.\n\n  Key concepts:\n    - Documentation graph: files (nodes) connected by links (edges)\n    - Entrypoint: starting file (default: README.md) at depth 0\n    - Reachability: files discoverable by following links from entrypoint\n    - Orphans: files not reachable from entrypoint\n\n  Common workflows:\n    1. Validate: mdite lint\n    2. Analyze: mdite deps <file>\n    3. Search: mdite files | xargs rg \"pattern\"\n    4. Export: mdite cat | pandoc -o docs.pdf\n";
export declare const MAIN_EXAMPLES = "\nEXAMPLES:\n  Validate your documentation:\n      $ mdite lint\n\n  Understand dependencies before refactoring:\n      $ mdite deps docs/api.md --incoming\n\n  List all reachable files and search:\n      $ mdite files | xargs rg \"authentication\"\n\n  Export documentation in dependency order:\n      $ mdite cat --order deps | pandoc -o docs.pdf\n\n  Initialize configuration:\n      $ mdite init\n";
//# sourceMappingURL=help-text.d.ts.map