Function code_scanning_incompatibility 

pub fn code_scanning_incompatibility(
    provider: Option<Provider>,
    tech: &str,
    forge: &str,
) -> Option<String>

Why the named code scanning provider cannot run at this (technology, forge), or None where it can or none is named.

One owner for the question, because two callers ask it and they must not disagree. Parameter resolution turns a reason into a refusal, so init, upgrade, adopt, and stage never record an answer they cannot honour. The projection reports the same reason as a record defect, because Params::from_record cannot fail and a hand-edited or foreign receipt reaches rk status through it: without this, a receipt naming a provider whose pair ships nothing would project nothing, name nothing, and read as clean.