I have four recordings under projects/demo-shop/recorded/ and I have been told to convert them rather than hand-write the features. Before I point it at anything that matters: what does sdods record convert write, and where? I do not want a generator rearranging files under me while I am reading something else.
Accepted answer
Nothing lands in the working tree. record convert hands the spec to the generator agent and the agent's output is a proposal — a directory under proposals/<id>/ with a manifest, the files it wants to add and a diff. Your features/, steps/ and pages/ are untouched until a person says otherwise.
sdods record convert projects/demo-shop/recorded/checkout.spec.ts
sdods proposals list
sdods proposals show <id>
sdods proposals accept <id>accept applies the files and then runs sdods lint, unless you pass --no-lint; --branch <name> puts them on a new git branch if you would rather review it as a pull request. reject takes a --reason.
The recording itself is never deleted, and it stays runnable under -l recorded whether you accept or not, so the conversion is additive in both directions.
If you want the shape without spending a model call:
sdods record convert projects/demo-shop/recorded/checkout.spec.ts --dry-runwhich prints the prompt and the plan and stops. --adapter fake is the other way to exercise the plumbing without a provider.
Having reviewed a handful of these, the three things worth actually reading in the proposal:
accept runs lint, a mistagged proposal fails there rather than landing quietlyThe roles guide also shows passing two recordings of the same flow at once, in which case the generator proposes a single Scenario Outline with the role in the examples table instead of two near-identical scenarios: record and playback with roles and environments.
Have a different question? Ask it.