Module config 

Configuration paths within project

Constants

DIR

Base configs directory

NODES_DIR

Node configs base directory

NODES_MECHA10_DIR

Framework node configs (@mecha10 scope)

SIMULATION_CONFIG

Simulation config file

SIMULATION_DIR

Simulation configs directory

Functions

behavior_config_candidates

The 2-tier config.json lookup candidates for a behavior, in override-precedence order (highest first): project (plain name) -> framework (@mecha10). A project-committed override beats the bundled framework default. There is no @local tier for behaviors (LAB-1990). See node_config_candidates for the sibling helper for nodes.

framework_behavior

Get config path for a framework-default behavior (bundled into the project at scaffold time under configs/behaviors/@mecha10/<name>/config.json).

framework_node

Get config path for a framework node

framework_node_dir

Get the framework node’s config directory (no config.json suffix) - the @mecha10 counterpart to framework_node, for callers that need the directory itself (e.g. to copy a whole config template tree into it) rather than the config.json file path.

node_config_candidates

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.

project_behavior

Get config path for a project behavior (plain name: configs/behaviors/<name>/config.json).

project_node

Get config path for a project node (plain name)