orke package save-draft
Apply the authoring AI's draft and its name to the execution definition.
When to use it
Apply the authoring AI's draft and its name to the execution definition.
Usage
Syntax · [ ] marks optional arguments
orke package save-draft --slug <string> --name <string> --expectedRevision <string> [--preferDraft <boolean>]Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Package identifier returned by list or create. |
--name | Required | New name or display name. |
--expectedRevision | Required | Definition revision read with get. |
--preferDraft | Optional | Save conflicting edits (draftConflicts), where another source changed the same part differently, using the draft's version. Use only after reviewing the conflict list. |
Common management options and errors →
Example
Terminal
orke package save-draft --slug package_slug --name "Organize meeting notes" --expectedRevision revision_from_getReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
PackageDescriptor: definition/revision/readError, runtime/target/allowedActions, completedStages/attention/recovery, draftConflicts/draftMerged
Behavior and states to watch
- Apply the existing package.draft.md and its name to the execution definition. Merge definition changes made elsewhere since the draft began, including run settings in the package window and direct file edits.
- If the same part was changed differently, do not save; return those parts in draftConflicts (kind, label, current, draft). Compare them, then save the draft's version with --preferDraft true, or use recover-draft to archive the draft and start again.