Expand description
The profile resolver — turning a parsed command into its behavior profile
(annex behavioral-taxonomy-engine). Runs via engine::bridge, which is
AUTHORITATIVE for every command it can resolve (engine_verdict(tokens).unwrap_or(legacy)
in cst::check::leaf_verdict) — there is no opt-out.
This file holds the dispatch (resolve) and the per-command resolve_* functions;
the shared toolkit they build on lives in submodules: [flags] (the getopt-style
flag walker), [locus] (classify_locus — the LocalLocus ladder that refines the
old is_safe_write_target boolean, v1.4 §2.2), and [capability] (the builders that
stamp out each Capability with the facet pairing its operation warrants).
Functions§
- resolve
- Resolve a command’s leaf tokens to its behavior profile, or
Noneif the command has no resolver yet (the caller then worst-cases / falls back to the legacy classifier — §0 fail-closed). Redirects, substitutions, and chain semantics are the surrounding CST’s job, not this leaf’s (annex…-engine§1).