call-graph-output

Render already-understood call paths, runtime flows, architecture relationships, or orchestration DAGs as compact plain-text graphs when a graph materially improves human understanding. Use for architecture explanations, execution traces, implementation summaries, review evidence, or delegated-work DAGs. Preserve the semantics supplied by the owning skill; do not invent architecture, dependencies, workers, edge types, or verification requirements. Do not emit a graph for every change. Prefer outcome/responsibility labels over filenames, show Production/Tests only when they materially differ, and compare planned vs actual graphs by contract/outcome rather than demanding structural equality.