Use local templates for config new

[waldekmastykarz]

Summary

• store the minimal JSON and YAML templates required by config new in this repository
• create new configuration files from packaged templates instead of downloading the full Toolkit snippet catalogs
• include the templates in build, publish, and installer outputs
• update the version-upgrade automation to maintain template schema URLs

Validation

• dotnet build DevProxy/DevProxy.csproj
• dotnet build DevProxy.Plugins/DevProxy.Plugins.csproj
• generated and validated JSON and YAML files with config new
• verified both templates are present in single-file publish output

[Copilot]

🟡 Changes recommended

The YAML template produces invalid generated configuration because its blank sequences parse as null.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This pull request switches config new to packaged local JSON/YAML templates and updates build and version-upgrade automation.

Changes:

• Adds and packages local configuration templates.
• Reads templates from the application directory.
• Updates schema URL maintenance automation.

File summaries

File	Reviewed change
DevProxy/DevProxy.csproj	Packages templates in build outputs.
DevProxy/config-templates/devproxyrc.yaml	Adds YAML template; blank sequences currently produce invalid null entries.
DevProxy/config-templates/devproxyrc.json	Adds JSON configuration template.
DevProxy/Commands/ConfigCommand.cs	Creates configurations from local templates.
.github/skills/upgrade-devproxy-version/SKILL.md	Documents template schema updates.
.github/skills/upgrade-devproxy-version/scripts/upgrade-version.sh	Updates template schema URLs.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.