StigCheckConfigTask

Per-module configuration validation task.

Performs two kinds of checks:

1. Path validation

Checks that all paths declared in a module's stig { element { ... } } block actually exist on disk:

• Repo roots referenced by this module

• topicsFile — the topics JSON

• interfacePointsAnnotationFile — the ASIL interface-points JSON

• interfacePointLocation — directory for interface definition files

• Patch files and their replaceFromFile targets

2. DSL consistency validation

Checks for contradictory or incomplete DSL settings:

• Analysis enabled without a native build provider (nativeBuild { bazel { } })

• softwareUnderAnalysis { requireExplicitIncludes = true } without include(...)

• interfacePoints { interfacePointMode = DSL_DECLARATION } without sources/sinks or entryPoints

• interfacePoints { interfacePointMode = SOURCES_* } without topicsFile or entryPoints

This catches configuration errors early (at configuration-check time) rather than deep inside the pipeline when a task fails with a cryptic error.

The root project registers a stigCheckConfig aggregator that depends on every submodule's instance of this task.

Checks current path existence, kind and containment on every invocation. The DSL snapshot records paths, not their filesystem state; hashing entire referenced repositories would do unnecessary work. Stable validation outputs leave downstream task reuse unaffected.