//! The Behavior panel's model half: the authored args of one `Behavior` seen as
//! an editable node graph. `path` addresses a place inside those args, `palette`
//! holds the closed node / expression vocabulary and the JSON a fresh one starts
//! as, `outline` flattens the whole asset into the panel's indented rows, `edit`
//! applies what a row's controls do, `clip` carries a list member from one place
//! to another, `filter` narrows a palette to what was typed into it, `navigate`
//! says where a step of the selection lands, `fault` resolves the checker's
//! complaint to the row it is about, and `trace` / `pulse` turn the runtime's
//! execution reports into the paths and fading highlights live debugging draws.
//! Nothing here touches the world or the HUD: the layout half is
//! `editor/behavior/panel.rs` and the actions live in `hook/edit/behavior.rs`.
//!
//! The panel edits the authored JSON directly rather than a typed twin, because
//! that JSON is exactly what `check_with_variables` reads -- so the status line
//! reports on the same value the build will.
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub
pub