Summary
archon-workflow-builder fails DAG-structure validation at load. Two example placeholders inside the generate-yaml prompt body are parsed as real cross-node references:
- Line 138:
const raw = String.raw`$other-node.output`;
- Line 179:
$nodeId.output is NOT shell-quoted in script bodies...
The loader scans prompt bodies for $<nodeId>.output references and requires each to resolve to an upstream sibling. Elsewhere in the same file (lines 126, 135, 157, 161, 169, 170) placeholders are already written as $<nodeId>.output — angle brackets escape them from the scanner because </> aren't valid in node IDs.
Reproduce
$ archon workflow list
...
archon-workflow-builder.yaml: Node 'generate-yaml' references unknown node '$other-node.output'
Observed on dev at ad13d83 (current HEAD). Severity: minor — workflow is bundled but not load-bearing; the rest of the system works.
Fix
Rewrite the two lines using the existing angle-bracket convention. PR to follow.
Summary
archon-workflow-builderfails DAG-structure validation at load. Two example placeholders inside thegenerate-yamlprompt body are parsed as real cross-node references:const raw = String.raw`$other-node.output`;$nodeId.output is NOT shell-quoted in script bodies...The loader scans prompt bodies for
$<nodeId>.outputreferences and requires each to resolve to an upstream sibling. Elsewhere in the same file (lines 126, 135, 157, 161, 169, 170) placeholders are already written as$<nodeId>.output— angle brackets escape them from the scanner because</>aren't valid in node IDs.Reproduce
Observed on
devatad13d83(current HEAD). Severity:minor— workflow is bundled but not load-bearing; the rest of the system works.Fix
Rewrite the two lines using the existing angle-bracket convention. PR to follow.