Added:

- `dcr gen` command for IDE integration and build tool support
    - `dcr gen project-info`: Output project metadata as JSON
    - `dcr gen compile-commands`: Generate `compile_commands.json` for clangd and clang-tidy
    - `dcr gen vscode`: Generate VS Code `.vscode/` integration (launch.json, tasks.json, settings.json)
    - `dcr gen clion`: Generate JetBrains CLion `.idea/` integration (run configurations, build targets)
- Full workspace support for all `gen` subcommands

docs/commands/dcr-run.md

@@ -8,6 +8,8 @@ Builds the project and runs the resulting binary.
 dcr run
 dcr run --debug
 dcr run --release
+dcr run --release --force
+dcr run --debug --clean
 ```
 
 ## Behavior
@@ -16,11 +18,20 @@ dcr run --release
 2. Reads `package.name`, `build.kind`, and optional `build.target`.
 3. Runs the same build flow as `dcr build`.
 4. Executes the built artifact path for the selected profile.
+5. If `[run].cmd` is set, runs that command instead of the built binary.
 
 ## Restrictions
 
 - If `build.kind = "staticlib"` or `build.kind = "sharedlib"`, `run` exits with error.
 - The profile is selected from the first argument.
+- `--force` skips build cache checks and recompiles.
+- `--clean` removes `target/<profile>` and `build.clean` paths before building.
+
+## `run.cmd` variables
+
+`run.cmd` supports the same variables as build steps: `{profile}`, `{version}`, `{version_major}`,
+`{version_minor}`, `{version_patch}`, `{version_suffix}`, `{version_suffix_dash}`.
+The command runs via `sh -c` on Unix and `cmd /C` on Windows.
 
 ## On build failure