version_create
Store a candidate state of editable files as a content-addressed snapshot or unified patch without changing the current base, so edits can be reviewed before proposal and launch.
Instructions
Store a candidate version of the editable files, either by snapshotting a complete scenario checkout or by applying a unified patch to a parent version. Use it after editing and before proposal_create and run_launch; use version_diff to review a stored change. Writes content-addressed snapshot files and appends a ledger event; it never adopts or changes the current base. Rejects edits outside the editable globs, unsafe paths and patches that do not apply. Returns {version, parent, changed}; identical content always gets the same version id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"config": "<config>"
},
"name": "version_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| patch | No | Unified Git-style patch text, as printed by `git diff`, applied to a temporary checkout of parent. Do not combine with directory. | |
| config | Yes | Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path. | |
| parent | No | Base version of the change: 64-character lowercase SHA-256 version id, as returned by version_create. Default: current base. | |
| directory | No | Path of a complete scenario checkout on the server host to snapshot. Defaults to the original scenario directory. Do not combine with patch. |