Doc system test

composition-run

CompositionOperator::execute_template flattens the tree, then for each node in run order: skips template groups, builds the node's answers (caller answers, then presets), serves it from the node cache or runs it through the coordinator, and adds its final answers to the shared answers so later nodes are not asked again. It stops early on a headless question. Then it layers all outputs and returns the file set, the answers, the coordinator sessions to release, and the post-template commands of the whole tree.

If two templates give one answer id different answer kinds (text vs boolean), the run fails with a type conflict. Found while reading, not run: headless keeps only the answers a template asked for, but the shared answers still start from every supplied answer, so unasked answers reach later templates.

Where it lives

  • sulfone.iridium/cyancoordinator/src/operations/composition/operator.rs
  • sulfone.iridium/cyancoordinator/src/operations/composition/state.rs

Stub: summary only.