Update Learning Hub for CLI v1.0.72–v1.0.75 changes

- Fix outdated /worktree and /move documentation: in v1.0.72 these were
  split into distinct commands (/worktree leaves uncommitted changes
  behind, /move carries them into the new worktree)
- Add /model plan command documentation (v1.0.74)
- Add claude-opus-5 to model examples in repository settings section (v1.0.75)
- Add Open Plugin Spec v1 / mcp.json manifest support note (v1.0.74)
- Update lastUpdated dates on both pages

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: github-actions[bot]

website/src/content/docs/learning-hub/copilot-configuration-basics.md

@@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics'
 description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-07-13
+lastUpdated: 2026-07-25
 estimatedReadingTime: '10 minutes'
 tags:
   - configuration
@@ -223,7 +223,7 @@ The `~/.agents/skills/` path aligns with the VS Code GitHub Copilot for Azure ex
 
 | Field | Description | Example values |
 |-------|-------------|----------------|
-| `model` | The AI model to use for this repository | `"claude-sonnet-4"`, `"gpt-4.1"`, `"claude-sonnet-5"` |
+| `model` | The AI model to use for this repository | `"claude-sonnet-4"`, `"gpt-4.1"`, `"claude-sonnet-5"`, `"claude-opus-5"` |
 | `effortLevel` | Reasoning effort level | `"low"`, `"medium"`, `"high"` |
 | `contextTier` | How much context to include | `"default"`, `"full"` |
 
@@ -449,6 +449,14 @@ The model picker opens in a **full-screen view** with inline reasoning effort ad
 
 **Model family aliases** (v1.0.64+): Instead of typing a full model name, you can use short family aliases in the model setting: `opus`, `sonnet`, `haiku` (Anthropic), and `gpt`, `gemini` (Google/OpenAI). The CLI resolves the alias to the latest available model in that family. This is especially useful in scripts or configuration files where you want to track the best model in a family without hardcoding a version string.
 
+**Plan mode model** (v1.0.74+): Use `/model plan` (or `/model --plan`) to pick a dedicated model for plan mode, separate from the model used in regular sessions. Pass a model id to set it, `off` to clear, or no argument to open the picker. The plan model automatically reverts to the session model when you leave plan mode:
+
+```
+/model plan                   # open the picker to choose a plan model
+/model plan claude-opus-5     # use Claude Opus 5 specifically for planning
+/model plan off               # clear the plan-mode model override
+```
+
 ### CLI Session Commands
 
 The `/settings` command (v1.0.61+) opens an interactive dialog to browse and edit all user settings in one place. Use it to discover available settings, toggle options, and update values without manually editing your config file:
@@ -541,7 +549,7 @@ The `/cd` command changes the working directory for the current session. Since v
 
 This is useful when you have multiple backgrounded sessions each focused on a different project directory.
 
-The `/worktree` command (v1.0.61+, also aliased `/move`) creates a new git worktree and switches into it, moving any uncommitted changes along. This lets you start working on a parallel branch without leaving your current terminal session:
+The `/worktree` command (v1.0.61+) creates a new git worktree on a new branch and switches into it, **leaving any uncommitted changes behind** in the original worktree. This is useful when you want to start fresh on a parallel task without disturbing work-in-progress:
 
 ```
 /worktree my-feature-branch
@@ -555,7 +563,17 @@ In v1.0.66+, you can pass a task description to `/worktree` to name the branch f
 
 This creates a branch named from your task description and begins working on it immediately, making it easy to spin up parallel work without stopping to think of a branch name.
 
-After the command runs, the session is inside the new worktree. Use this when you want to work on a second task in parallel without stashing changes or opening a new terminal. In v1.0.64+ you can also use the experimental `--worktree` flag at startup (`copilot -w [name]`) to create or reuse a worktree under `<repo>.worktrees/` before the session begins.
+The `/move` command (v1.0.72+) is the complement to `/worktree`: it **carries your uncommitted changes** into the new worktree. Use `/move` when you've started work in one context and want to continue it in an isolated branch:
+
+```
+/move my-feature-branch    # move uncommitted changes to a new worktree
+```
+
+In summary:
+- **`/worktree`** — create a new worktree and leave uncommitted changes behind
+- **`/move`** — create a new worktree and carry uncommitted changes with you
+
+In v1.0.64+ you can also use the experimental `--worktree` flag at startup (`copilot -w [name]`) to create or reuse a worktree under `<repo>.worktrees/` before the session begins.
 
 The `/every` command (also available as `/loop` since v1.0.64) schedules a recurring prompt to run automatically at a specified interval. The companion `/after` command runs a prompt once after a specified delay. Both are useful for self-paced automation — polling for results, periodically summarizing progress, or triggering other slash commands on a timer:
 

website/src/content/docs/learning-hub/installing-and-using-plugins.md

@@ -3,7 +3,7 @@ title: 'Installing and Using Plugins'
 description: 'Learn how to find, install, and manage plugins that extend GitHub Copilot CLI with reusable agents, skills, hooks, and integrations.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-07-13
+lastUpdated: 2026-07-25
 estimatedReadingTime: '8 minutes'
 tags:
   - plugins
@@ -74,6 +74,8 @@ The `plugin.json` manifest declares what the plugin contains:
 }
 ```
 
+*(v1.0.74+)* Copilot CLI also supports the **Open Plugin Spec v1** (`mcp.json`) format for plugin manifests. This means plugins authored for other MCP-compatible tools can be installed directly in Copilot CLI without conversion, and you can use `mcp.json` as the manifest file alongside or instead of `plugin.json`.
+
 ## Why Use Plugins?
 
 You might wonder: why not just copy agent files into your project manually? Plugins provide several advantages: