What problem does it solve? Submitting multiple dependent Invoker workflows headlessly requires manually copying workflow IDs between plans and wiring cross-workflow merge-gate dependencies by hand, which is error-prone and slow from the CLI. ## Core Features & Use Cases - Headless chain submission: Submits a sequence of workflow plans where each downstream workflow is gated on the previous workflow's merge gate, using --no-track so submissions return immediately. - Automatic ID resolution: Renders template placeholders like __UPSTREAM_WORKFLOW_ID__ with persisted workflow IDs resolved by name, avoiding transient ID races. - Stacking onto running workflows: The --onto-workflow flag attaches the chain head onto an already-running upstream by setting plan[0] baseBranch to that workflow's featureBranch. - Use Case: You have a feature split across three stacked workflows. Provide the first full plan plus two templates with the externalDependencies placeholder, run the script once, and receive the persisted IDs WF1, WF2, WF3 in chain order. ## Quick Start Run the submit-workflow-chain script with my first workflow plan and the downstream template files to submit the whole gated chain headlessly.
