Release v1.21.0

plugins/github-copilot-modernization/.mcp.json

@@ -5,7 +5,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@microsoft/github-copilot-app-modernization-mcp-server@1.20.0",
+        "@microsoft/github-copilot-app-modernization-mcp-server@1.21.0",
         "--callerType",
         "github-copilot-modernization-plugin"
       ],

plugins/github-copilot-modernization/agents/assessment-coordinator.agent.md

@@ -1,7 +1,7 @@
 ---
 name: assessment-coordinator
 description: Coordinates assessment phase using MCP tools
-model: Claude Opus 4.6
+model: 'Claude Opus 4.8'
 user-invocable: false
 hooks:
   UserPromptSubmit:
@@ -31,7 +31,7 @@ You coordinate the assessment phase by detecting the project language, invoking
 - `project-path`: Absolute path to project root
 - `config` (Java only, optional): Assessment configuration overrides. **IMPORTANT: Do NOT pass `config` at all unless the user explicitly specifies configuration. When passing, only include the specific fields the user literally mentioned — never auto-fill, infer, or derive values for unspecified fields. For example, if the user says "for azure container apps and AKS", only set `targetComputeServices` — do NOT infer `enableContainerization: true` or any other field the user did not explicitly name.** Supported fields:
   - `domains`: Array of domain names. Acceptable values: `java-upgrade`, `cloud-readiness`, `security`. Default: `["java-upgrade", "cloud-readiness"]`. Silently drop any unrecognized values.
-  - `analysisCoverage`: `issue-only` | `source-only` | `full`
+  - `analysisCoverage`: `issue-only` | `full`
   - `targetRuntime`: `openjdk11` | `openjdk17` | `openjdk21` | `openjdk25`
   - `targetComputeServices`: Array of `azure-aks` | `azure-appservice` | `azure-container-apps`
   - `enableContainerization`: boolean

plugins/github-copilot-modernization/agents/execution-coordinator.agent.md

@@ -1,7 +1,7 @@
 ---
 name: execution-coordinator
 description: Coordinates execution phase using multi-agent orchestration
-model: Claude Opus 4.6
+model: 'Claude Opus 4.8'
 user-invocable: false
 hooks:
   UserPromptSubmit:

plugins/github-copilot-modernization/agents/modernize-azure-dotnet.agent.md

@@ -41,7 +41,7 @@ tools:
   - shell
   - todo
 
-model: Claude Sonnet 4.6
+model: 'Claude Sonnet 4.6'
 
 hooks:
   UserPromptSubmit:
@@ -99,11 +99,19 @@ When you receive the migration context from #appmod-run-task, use these values t
 ### 1. Planning Phase (REQUIRED FIRST STEP)
 **Before any migration work, I MUST call `appmod-run-task` first.** If the delegation prompt names a kbId (any of: `kbId: <X>`, `[kbId: <X>]`, `by kbId: <X>`, `` Use the builtin skill: `<X>` ``), I pass **only** `kbId` (plus `workspacePath` and `language`) — I do NOT also pass `scenario`, `skillId`, or `taskId`. Otherwise, I pass **only** `scenario` set to the goal sentence from the prompt. My single source of truth is the delegation prompt text — I do NOT read `tasks.json` or any other file to derive these parameters.
 
-This tool will provide instructions for generating `plan.md` and `progress.md` files in `.github/modernize/code-migration`.
+After `appmod-run-task` returns the migration context, I MUST save tracking artifacts before any code changes:
+
+1. **Create `{{planFile}}`**: Save the complete migration plan (session ID, scope, files to change, dependency/config/code changes, validation steps) to `{{planFile}}` in `{{workspacePath}}`. The plan must be detailed enough for the Execution Phase to follow without re-discovery.
+2. **Create `{{progressFile}}`**: Save initial progress (plan generation=completed; version control, code migration, verification, summary=pending) to `{{progressFile}}`.
+3. **Preview**: Open both files with `appmod-preview-markdown` when available.
+
+Do NOT proceed to version control or code changes until both `{{planFile}}` and `{{progressFile}}` exist.
 
 ### 2. Execution Phase
 **I MUST strictly follow the plan and progress files.**
 
+I MUST read `{{planFile}}` as the source of truth for scope, files, dependencies, and validation steps before starting migration phases. If missing, return to Planning Phase first.
+
 Migration phases in order:
 1. **Analysis**: Analyze the solution structure and dependencies
 2. **Dependencies**: Update NuGet packages and project references, search knowledge base "dotnet-dependency-management" for dependency management best practices

plugins/github-copilot-modernization/agents/modernize-azure-java.agent.md

@@ -61,7 +61,7 @@ tools:
   - appmod-mcp-server/appmod-install-jdk
   - appmod-mcp-server/appmod-install-maven
 
-model: Claude Sonnet 4.6
+model: 'Claude Sonnet 4.6'
 
 hooks:
   UserPromptSubmit:

plugins/github-copilot-modernization/agents/modernize-java-assessment.agent.md

@@ -1,6 +1,6 @@
 ---
 name: modernize-java-assessment
-description: Assess codebases with evidence-based findings
+description: 'Assess codebases with evidence-based findings'
 user-invocable: true
 tools: ['tool_search', 'vscode/toolSearch', 'agent', 'search', 'edit', 'web', 'todos',
 'appmod-run-assessment-action', 'appmod-cwe-rules-assessment', 'appmod-java-cve-assessment', 'appmod-run-assessment-report',