Skip to main content

permissions_rules_patterns

supercode_harness::configfile

Function permissions_rules_patterns 

Source 
pub fn permissions_rules_patterns(
    cap: &CapabilityConfig,
) -> (Vec<String>, Vec<String>)
Expand description

P4 (design §5.2 “P4”): read capabilities.permissions.rules.deny/ .allow (module 11’s two pattern arrays) into (deny, allow) glob pattern lists — the S-sized generalization of auto_approved_tools this phase lands, NOT the full P5 deny→ask→allow priority engine. cap is the already-fetched capabilities.permissions table (both this resolver’s materialize_config and the CLI’s own build_config fetch it themselves first, since each has a different container type to fetch it FROM — a HarnessConfig vs a BTreeMap on FileConfig). Empty Vecs when the table or either key is absent — the default, byte-identical-to-today shape.