Config and triage

A single inclusa.config.json at your project root holds the defaults a team settles once and then stops arguing about.

Defaults a team agrees once

The config sets the target level, the crawl limits, the scope, the default save destination, the screenshots toggle, and the CI gate defaults. It is read fresh on every scan, so edits take effect with no restart.

Disable versus triage

Disabling a rule removes it from the scan entirely, so it is not run and not shown. Triage is different: a known finding is marked and set aside, excluded from the totals and the conformance verdict, but still shown in a triaged section. Nothing is silently dropped.

A reason is required

Every triage entry must carry a reason, and an entry with no reason is refused with a warning. You can narrow a triage to a selector or a page glob, and add a category. This keeps reports signal rich on purpose: a reader can always see what was set aside and why.