cascade-cfg is a standalone crate that defines Cascade's configuration details; it turned out to be quite useful for #684. A long time ago @ximon18 had mentioned doing the same for policy, as it would also help with ods2cascade; I think it would also help with testing here. I don't think policy details should go in cascade-cfg, so I guess a new cascade-policy crate is necessary. This is mostly about moving files around. Though we need to decide what happens to the serialization of policy within state files (where do those serde definitions go).
cascade-cfgis a standalone crate that defines Cascade's configuration details; it turned out to be quite useful for #684. A long time ago @ximon18 had mentioned doing the same for policy, as it would also help withods2cascade; I think it would also help with testing here. I don't think policy details should go incascade-cfg, so I guess a newcascade-policycrate is necessary. This is mostly about moving files around. Though we need to decide what happens to the serialization of policy within state files (where do those serde definitions go).