pub fn node_config_candidates(node_name: &str) -> [String; 2]Expand description
The 2-tier config.json lookup candidates for a node, in canonical resolution order:
framework (@mecha10) -> project (plain name). This is the ONE place that knows the tier
order/naming convention for “does this node have a config.json, and if so which scope is
it in” - callers that need to check both tiers (e.g. “use the first one that exists on
disk”) should use this rather than hand-rolling the same format!()/literal strings
themselves, which is exactly what caused LAB-1982.