User Guide | Engineering Case Study
TODO: Explain script files and when users should use them.
TODO: Explain how the current actions become editable command history, which edits are valid, how applying an edit changes the session, and how to save the resulting commands as a
.docfd-script.
RECORDING TODO (20–30 seconds): Perform two or three search/filter actions, open editable command history, change or remove one action, apply the edited history, and save it as a script. This should be a dedicated clip because editable/replayable history is unusual and difficult to communicate with a screenshot.
TODO: Document
--script,--start-with-script, script-name resolution, and listing available scripts.
OPTIONAL RECORDING TODO (15–20 seconds): Show
docfd --list-scripts, launch a script by name without its.docfd-scriptextension, and show the resulting session. Prefer a terminal transcript if it communicates the same information clearly.
TODO: Add examples combining scripts and project configuration.