Fix GitHub Actions pipeline failures across CI, docs, and release workflows

[Copilot]

CI, documentation, and minimal-versions jobs were failing due to ANSI color detection, missing dependencies, test configuration, and dead link checking issues.

Changes

Color support detection for CI environments

Updated supports_ansi_colors() in src/report/mod.rs to recognize GITHUB_ACTIONS and CI environment variables:

fn supports_ansi_colors() -> bool {
    if std::env::var("NO_COLOR").is_ok() {
        return false;
    }
    
    // GitHub Actions and other CI systems support ANSI colors
    if std::env::var("GITHUB_ACTIONS").is_ok() || std::env::var("CI").is_ok() {
        return true;
    }
    
    std::env::var("TERM").is_ok_and(|term| term != "dumb")
}

Previously failed when CARGO_TERM_COLOR=always was set but TERM was unset or "dumb" in CI.

Minimal-versions job dependencies

Added cargo install cargo-hack to .github/workflows/ci.yml - required by cargo-minimal-versions but not installed.

Test configuration isolation

Modified test_check_command in src/main.rs to create explicit test config instead of relying on ambient guardian.yaml discovery, which has exclusions that break test assertions.

Documentation link checking

• Added ignore patterns to .github/mlc_config.json for unpublished crates.io URLs
• Created CONTRIBUTING.md referenced in README

Code formatting

Applied rustfmt across codebase.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR addresses CI/documentation workflow failures by making report color support detection CI-aware, ensuring minimal-versions tooling dependencies are installed, and tightening test isolation around config discovery. It also updates documentation link-check configuration and adds a contributing guide, alongside broad rustfmt formatting changes.

Changes:

• Update ANSI color support detection to treat GITHUB_ACTIONS/CI as color-capable environments.
• Fix CI minimal-versions job by installing cargo-hack in addition to cargo-minimal-versions.
• Make test_check_command use an explicit generated config instead of relying on ambient guardian.yaml discovery.
• Adjust markdown link-check ignores and add CONTRIBUTING.md; apply rustfmt across touched Rust modules.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/report/mod.rs	CI-aware ANSI color support detection; formatting-only changes elsewhere.
src/main.rs	Test now writes and uses an explicit temp config; formatting in command dispatch/logging.
src/config/mod.rs	Formatting updates; minor iterator/regex builder formatting changes.
src/analyzer/mod.rs	Formatting updates around rule wiring and parallel analysis loop.
src/analyzer/rust.rs	Formatting updates in type checks and test-only self-validation helpers.
src/lib.rs	Formatting updates around validator construction/await chains and cache logic.
src/domain/violations.rs	Formatting updates in report/error constructors and a test assertion.
src/patterns/mod.rs	Formatting updates across pattern engine message construction and visitors.
src/patterns/path_filter.rs	Formatting updates in pattern structs, directory walking, and test helper.
src/cache/mod.rs	Formatting updates in cache metadata default implementation.
.github/workflows/ci.yml	Install cargo-hack for minimal-versions job.
.github/mlc_config.json	Add ignore patterns for crates.io URLs and CONTRIBUTING.md.
CONTRIBUTING.md	New contributor guide referenced by docs.

[Copilot]

supports_ansi_colors() treats NO_COLOR as “no ANSI support”, but validate_capabilities() will then hard-fail when use_colors is true (the default). That makes the tool error out in environments where NO_COLOR is set, instead of simply disabling colors as the variable intends. Consider honoring NO_COLOR by forcing use_colors = false (or skipping the capability error when NO_COLOR is present), so NO_COLOR never causes an otherwise-valid run to fail.

[Copilot]

Now that CONTRIBUTING.md is added to the repo and linked from the README, ignoring CONTRIBUTING.md here defeats the purpose of the link check (a future broken/renamed file link would no longer be caught). Prefer removing this ignore entry and letting the checker validate the relative link.

Suggested change

	},
	{
	"pattern": "^CONTRIBUTING\\.md$"

[Copilot]

For CI stability/reproducibility, cargo install steps should generally use --locked (and optionally --force to avoid failures if the tool is already installed on the runner). Without --locked, upstream dependency changes can break installs and cause intermittent pipeline failures.