CLI project regeneration overwrites reviewed NuGet versions #422

Regenerating an existing CLI tool can silently replace its reviewed project configuration and undo dependency updates.

Observed with AutoSDK 0.35.0-preview.2.89: tryAGI/Revocalize#55 changes only the generated CLI project, downgrading MinVer 8.0.0 to 7.0.0 and System.CommandLine 2.0.13 to 2.0.7. The repository's update script deletes the whole CLI directory before calling autosdk cli-project, so even an owner-maintained project is replaced by scaffold defaults.

The generator should offer an explicit way to regenerate command sources while retaining an existing .csproj byte-for-byte (including pinned versions, central-version expressions, owner properties and build metadata). A missing project should still be scaffolded. Keeping this opt-in preserves existing default behavior and avoids partial XML rewrites that lose owner settings. The caller must retain the project file rather than deleting its directory first.

Regression coverage should exercise both existing and missing projects, opt-in and default behavior, preservation of owner settings/versions, and regeneration of changed command sources. Real repository validation still needs the complete dependency graph, vulnerability scan, build and no-cost/native checks before accepting the resulting CLI package.