deepseek-harness/examples/acp-agent/tests/snapshots/workspace-edit/input.json

{
  "steps": [
    { "op": "initialize" },
    { "op": "newSession" },
    { "op": "prompt", "text": "A file named greeting.txt in the current directory contains one word. Use the bash tool to append a second line containing the word WORLD to it (so it has two lines), then read the file back with `cat greeting.txt` to confirm, and reply with the single word DONE. Use a single bash call per action." }
  ]
}
feat(acp-example): per-scenario workspace/ seeding + a real file-edit scenario Establishes the standard way to give a snapshot scenario a non-empty starting workspace: an optional `<scenario>/workspace/` directory whose contents the harness copies into the temp cwd before the run (for both record and replay), so the agent's bash tools see the seeded files. The cwd is normalized in the goldens, so seeded paths stay stable. The new `workspace-edit` scenario demonstrates the full read→write→verify cycle on a seeded file: it ships `workspace/greeting.txt` ("hello"), prompts the agent to append a WORLD line and cat it back. The recorded log captures the real bash edits (`echo WORLD >> greeting.txt`, then `cat` showing `hello\nWORLD`), and it replays deterministically with no key. Also hardens runScenario teardown (Codex review): workspace seeding and spawn now run inside the try whose finally removes both temp dirs, so a seeding/spawn failure can't leak them. Documents the convention in the RFC + example README. 2026-06-19 10:01:42 +08:00			`{`
			`"steps": [`
			`{ "op": "initialize" },`
			`{ "op": "newSession" },`
			{ "op": "prompt", "text": "A file named greeting.txt in the current directory contains one word. Use the bash tool to append a second line containing the word WORLD to it (so it has two lines), then read the file back with `cat greeting.txt` to confirm, and reply with the single word DONE. Use a single bash call per action." }
			`]`
			`}`