Copy the checked-in ODW workflow into the sidecar, then launch it from the
sidecar while using the target project as --source.
cp /path/to/df12-build/workflows/df12-build-odw.js \
"$SIDECAR/df12-build-odw.js"
odw run "$SIDECAR/df12-build-odw.js" \
--source "$PROJECT" \
--config "$SIDECAR/odw.config.json" \
--args @"$SIDECAR/args.json"
Use an absolute or fully expanded sidecar path for the workflow script. When
--source is present, ODW anchors relative workflow paths under the source
project, not under the shell's current working directory.
Start normal workshop runs in the background. Supervise them with odw status,
odw logs, odw result, and the ODW dashboard. Keep operator-notes.md
current enough that another operator can continue after context compaction.
When adopting a newer checked-in workflow into an existing sidecar, audit
args.json before relaunching. Older sidecars may still carry Codex-only
planAdapter, reviewAdapter, or assessmentAdapter overrides, and those
overrides deliberately win over the workflow defaults.