docs: refresh App workshop with learner-created skills and QA

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

Author: GeekTrainer

AUTHORING.md

@@ -15,7 +15,7 @@ copilot-workshops/
 │   ├── cli/                     ← Copilot CLI lessons (0-prerequisites.md + numbered exercises)
 │   ├── vscode/                  ← VS Code lessons (0-prerequisites.md + numbered exercises)
 │   ├── cloud/                   ← Cloud agent lessons (0-prerequisites.md + numbered exercises)
-│   ├── app/                     ← GitHub Copilot app lessons (setup folded into Exercise 1)
+│   ├── app/                     ← GitHub Copilot app lessons (setup 0–1, core modules 2–10)
 │   ├── es-es/ ja-jp/ ...        ← Translated locale trees (currently the app harness)
 │   └── _images/                 ← Screenshots and diagrams (shared across locales)
 ├── website/                     ← Optional Astro + Starlight publisher

docs/README.md

@@ -27,7 +27,7 @@ GitHub Copilot inside **Visual Studio Code** and GitHub Codespaces. Work with Co
 
 ### 🤖 [Copilot App](app/)
 
-The **GitHub Copilot app** — a desktop application built on Copilot CLI. Run parallel agent sessions, switch session modes, collaborate on canvases, and manage GitHub issues and pull requests natively — including **Agent Merge**, which shepherds a pull request through rebases, review feedback, CI fixes, and merge.
+The **GitHub Copilot app** — a desktop application built on Copilot CLI. Follow the same setup and nine core modules through the star-rating, instructions, filtering, skill, MCP, QA, and feature-PR workflow, using the app's isolated sessions and **Agent Merge**. Create and merge a repository-backed canvas as the fourth pull-request milestone, then wrap up.
 
 ### ☁️ [Copilot Cloud Agent](cloud/)
 

docs/app/0-prerequisites.md

@@ -15,18 +15,18 @@ In this lesson, you will:
 
 ## Install Node.js
 
-Several lessons ask an agent to build features and run the Tailspin Toys test suite locally, which needs **[Node.js][nodejs]** — the only runtime the project requires. Install version **22 or newer**; the current **LTS** release is a safe choice.
+Several lessons ask an agent to build features and run the Tailspin Toys test suite locally, which needs **[Node.js][nodejs]**. Use **Node.js 22.13 or later**, and confirm the supported version in your checkout's `package.json` and README.
 
 The simplest option on every platform is the official installer:
 
 1. In your operating system, open a terminal window using Windows Terminal, macOS terminal, or whatever you typically use.
-2. Run the following command to confirm you have at least Node.js 22 or higher installed:
+2. Run the following command to confirm you have Node.js 22.13 or later installed:
 
     ```shell
     node --version
     ```
 
-3. If you see `v22` or a higher number, you can skip to the next section!
+3. If the reported version is at least `v22.13.0` and supported by the project, you can skip to the next section.
 
 > [!TIP]
 > You only need to complete these steps if you don't have Node installed, or you need to update.
@@ -41,10 +41,10 @@ The simplest option on every platform is the official installer:
     node --version
     ```
 
-9. You should see `v22.x.x` or higher.
+9. Confirm the reported version is at least `v22.13.0` and supported by the project.
 
-> [!TIP]
-> Prefer containers? If you have **[Docker][docker]**, you can use the repository's [dev container][dev-containers] instead of installing Node.js locally — it bundles Node for you. You don't need both.
+> [!IMPORTANT]
+> This App path uses local worktrees. A runtime installed only in a container is not available to those local sessions. Each worktree also needs the project dependencies and Playwright Chromium for E2E checks. Follow the learner repository's README when preparing a worktree, and review any installation request before approving it.
 
 ## Set up the lab repository
 
@@ -64,6 +64,8 @@ You'll work against your own copy of the Tailspin Toys project. Create it now fr
 > [!NOTE]
 > When you create your repository from the template, a backlog of GitHub issues is created for you automatically. You'll work from these issues throughout the workshop — there's nothing to file yourself.
 
+Use a fresh copy of the revised template: it includes repository instructions, application code, tests, and an existing canvas extension, but no supplied custom agents or skills. You will create your own quality-checks skill and QA profile during the workshop. If you use an older copy, inspect existing customizations rather than overwrite them.
+
 ## Summary and next steps
 
 You're set up! You installed Node.js so the project can build and test on your machine, and you created your own copy of the Tailspin Toys repository from the template.
@@ -79,7 +81,5 @@ Next, you'll install the GitHub Copilot app, connect the repository you just cre
 [next-lesson]: ../1-install-copilot-app/
 [nodejs]: https://nodejs.org/
 [node-download]: https://nodejs.org/en/download
-[docker]: https://www.docker.com/products/docker-desktop/
-[dev-containers]: https://code.visualstudio.com/docs/devcontainers/containers
 [template-repository]: https://docs.github.com/repositories/creating-and-managing-repositories/creating-a-template-repository
 [about-copilot-app]: https://docs.github.com/copilot/concepts/agents/github-copilot-app

docs/app/1-install-copilot-app.md

@@ -41,23 +41,23 @@ To use the GitHub Copilot app the first step, as you might imagine, is to instal
 
 With your project connected, take a moment to learn your way around. The app organizes everything into a few areas in the sidebar:
 
-- **Sessions** — where agents do their work. Each session runs in its own isolated workspace, so you can run several at once without their changes colliding. You'll start your first session in the next lesson.
+- **Sessions** — where agents do their work. For this workshop, choose a **new working tree** so each PR milestone has an isolated checkout and branch. Other workspace choices exist, but are not used here.
 - **Quick chats** — lightweight conversations for questions and brainstorming that don't need a branch or workspace of their own. You'll try one at the end of this lesson.
 - **My work** — your issues and pull requests, surfaced through the app's **native GitHub integration**. From here you can browse and filter issues and pull requests, check CI status, start a session from an issue, and review pull requests — all without leaving the app.
-- **Automations** — saved agent tasks that run on a schedule or on demand. You'll create one near the end of the harness.
+- **Customize** — discover and manage MCP servers, skills, and canvases. You'll use it to configure Playwright MCP.
+- **Automations** — saved agent tasks that run on a schedule or on demand. The wrap-up links to these as a next step, not another workshop exercise.
 
 ### Find your seeded backlog
 
 Because the app integrates with GitHub natively, the work waiting in your repository shows up right inside the app. When you created your repository from the template, a backlog of issues was filed for you — let's confirm it's there.
 
 1. Select **My work** in the sidebar.
-2. The template seeded eight issues in your backlog. This harness focuses on the following three — confirm you can see them:
+2. Find these issues by title rather than assuming their issue numbers:
 
    - Allow users to filter games by category and publisher
    - Update our repository coding standards
-   - Implement pagination on the game list page
 
-3. Select an issue to read its details. Each issue is also a launch point for an agent session — you'll start work from these issues later in the harness.
+3. Select an issue to read its details. Each issue is also a launch point for an agent session — you'll start work from these issues later in the harness. Other backlog issues provide context for the canvas, not another implementation task.
 
 > [!NOTE]
 > The list of items in My work is automatically filtered to only display items from the repositories you've added to Copilot app. Want to see work items from other repos? Add them to the app!
@@ -84,15 +84,21 @@ Congratulations! You've installed the GitHub Copilot app, connected your project
 - get oriented in the workspace and find your seeded backlog in **My work**.
 - use a quick chat to ask a fast, throwaway question.
 
-Next, you'll start your first agent session and make your first change to the project — showing a star rating on the game cards. Continue to [Lesson 2 - Running your first agent session][next-lesson].
+## Keep PR milestones separate
+
+You will merge four PRs: star ratings; instructions with a small demonstration; filtering with the skill, QA profile, and tests; then the triage canvas. Use one branch per PR milestone. Lessons 4–8 stay in the same filtering session, worktree, and branch, with checkpoint commits rather than extra PRs.
+
+A new App worktree can start from stale local state. Before each new milestone edits files, fetch the repository and fast-forward the new session branch to the latest `origin/main`. The next lessons show this explicitly. Do not stack branches, cherry-pick earlier work, or switch an active filtering session to another branch.
+
+Next, you'll start your first agent session and make your first change to the project — showing a star rating on the game cards. Continue to [Lesson 2 - Add star ratings: a quick win][next-lesson].
 
 ## Resources
 
 - [About the GitHub Copilot app][about-copilot-app]
 - [Getting started with the GitHub Copilot app][getting-started]
 - [Working with agent sessions in the GitHub Copilot app][agent-sessions]
 
-[ex0]: ../0-prerequisites/
+[previous-lesson]: ../0-prerequisites/
 [next-lesson]: ../2-add-star-rating/
 [about-copilot-app]: https://docs.github.com/copilot/concepts/agents/github-copilot-app
 [getting-started]: https://docs.github.com/copilot/how-tos/github-copilot-app/getting-started

docs/app/8-review.md docs/app/10-review.mddocs/app/8-review.md renamed to docs/app/10-review.md

@@ -1,44 +1,43 @@
 ---
-title: "Lesson 8 - Review and next steps"
-description: "Recap the GitHub Copilot app harness, automate recurring work, and explore where to go next."
+title: "Lesson 10 - Wrap-up and next steps"
+description: "Recap the nine core App modules, four PR milestones, and reusable quality workflow, then explore further resources."
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-09-11
 ---
 
 Over the last several lessons, you took a feature from idea to merge with the GitHub Copilot app, including:
 
 - connecting a repository and orienting to the app's workspace and your seeded backlog.
 - starting sessions from a direct task and from issues, and using Plan and Autopilot modes to control how the agent works.
-- guiding the agent with custom instructions and a reusable skill.
+- guiding the agent with custom instructions, then asking it to create a reusable skill with shell scripts that you inspected and ran for lint, unit tests, end-to-end tests, and type checks.
 - testing your work with the Playwright MCP server in a real browser.
+- creating and selecting a QA custom agent to assess requirements, coverage, skill-script results, and browser evidence.
 - collaborating with the agent on a shared canvas.
-- shipping changes up a ladder of merge automation — from merging on github.com yourself to letting **Agent Merge** land a pull request.
+- explicitly merging the early PRs yourself, then authorizing **Agent Merge** within the feature and canvas PR workflows.
 
-Let's automate some recurring work, talk through best practices, and look at where to go next.
+Setup Lessons 0–1 led into nine core modules, Lessons 2–10. Take a moment to review the artifacts and where to go next; this wrap-up does not launch another hands-on task.
 
-## Automate recurring work
+## What you shipped
 
-The app can run agents for you on a schedule or on demand through **automations** — great for routine tasks like triaging new issues or recapping recent activity. Let's create a simple, non-destructive one.
+The workshop has four PR milestones, each on its own branch from updated `main`:
 
-1. Select **Automations** in the sidebar, then select **New automation**.
-2. Give it a name, such as `Recap my recent work`.
-3. Choose a trigger. **Manual** lets you run it on demand; **On a schedule** runs it automatically; **When an issue is created** reacts to new issues. Choose **Manual** for this lesson.
-4. Enter a read-only prompt so the automation can't change anything, for example:
+1. **Star ratings:** display the existing `starRating` and an explicit unrated state on game cards.
+2. **Instructions and demonstration:** add the documentation convention and verify its effect on a small real code change.
+3. **Filtering and quality workflow:** implement the issue, create the shell-bundled `quality-checks` skill and QA profile, and include the associated tests.
+4. **Repository-backed triage canvas:** share a board that adds issue context without automatically implementing another feature.
 
-   ```plaintext
-   Summarize the pull requests merged in this repository over the last week, and list any issues still open in the backlog.
-   ```
+Lessons 4–8 used the same filtering session, worktree, and branch. Checkpoint commits preserved progress within PR 3; skills, MCP configuration, and QA did not need separate feature branches. Each later milestone began only after the earlier PR merged and the fresh session branch was updated from `origin/main`.
 
-5. Pick the project (your Tailspin Toys repository) and create the automation.
-6. Run it on demand to see the result.
+## Different kinds of verification
 
-> [!TIP]
-> Automations can run locally or in the cloud. Enable **Run in the cloud** and pick the **Tools** an automation may use when you want it to run unattended on a schedule. Keep scheduled automations scoped and non-destructive until you trust their output.
+The early features used existing npm checks. Filtering added your manual browser inspection. The skill made the four checks repeatable through bundled scripts, MCP added direct agent browser observations, and QA combined requirements and coverage with final verification. The PR reused QA evidence only while it applied to the submitted revision.
+
+Tests added should close genuine gaps; a QA run that needs no new tests can be correct. Missing tools, skipped checks, and failures are visible blockers, not passes. Review code and evidence before authorizing merge, and refresh affected evidence after changes.
 
 ## Best practices
 
-When using any AI tool, the infrastructure around it drives the quality of what you get out. Instructions files, skills, and custom agents all played a part in this workshop — invest in them and reuse them across sessions.
+When using any AI tool, the infrastructure around it drives the quality of what you get out. You created instructions, a skill, and a QA profile in this workshop — review them and reuse them across sessions. Custom agents define specialist roles and instructions, with available tools governed by configuration and harness permissions; skills package reusable task instructions, executable scripts, and supporting resources loaded on demand. A custom agent can execute scripts too, including those bundled with a skill. Confirm actual script execution and custom-agent selection rather than relying on a convincing description.
 
 Match the **mode and model** to the task. Use **Plan** to think through an approach before building, **Interactive** to stay in the loop on focused changes, and **Autopilot** only for well-scoped, isolated tasks. Choose a faster model for routine edits and a more capable model with higher reasoning effort for complex work.
 
@@ -49,6 +48,7 @@ Context still matters as much as infrastructure. Clearly describing *what* you w
 You've covered the core workflow. A few more features worth a look:
 
 - **Quick chats** for fast, throwaway questions that don't need a full session.
+- [**Automations**][using-automations] for recurring or on-demand tasks such as summarizing recent work. Review the schedule, permissions, and scope before adopting one; creating an automation is a next step, not part of this workshop.
 - **Rubber duck** to talk through a problem and get high-signal feedback before you build.
 - [**Custom agents**][custom-agents] to package a role, its tools, and its instructions for repeatable, specialized work.
 - [`/chronicle`][chronicle] to generate a narrative of what happened in a session.
@@ -60,7 +60,7 @@ You've covered the core workflow. A few more features worth a look:
 
 The best way to improve with any tool is to keep using it! Use it for production code, for hobby code, for the little app you've had in mind for years but never got around to building. Share your learnings with your team, and learn from theirs. And, as always, explore the documentation.
 
-If you'd like to explore more of the GitHub Copilot ecosystem, check out the [VS Code harness](../../vscode/), the [Copilot CLI harness](../../cli/), or the [Cloud agent harness](../../cloud/).
+If you'd like to explore more of the GitHub Copilot ecosystem, check out the [VS Code harness][vscode-harness], the [Copilot CLI harness][cli-harness], or the [Cloud agent harness][cloud-harness].
 
 ## Resources
 
@@ -71,6 +71,10 @@ If you'd like to explore more of the GitHub Copilot ecosystem, check out the [VS
 - [Working with canvas extensions][canvas-docs]
 - [About cloud and local sandboxes][sandboxes]
 
+[previous-lesson]: ../9-canvases/
+[vscode-harness]: ../../vscode/
+[cli-harness]: ../../cli/
+[cloud-harness]: ../../cloud/
 [about-copilot-app]: https://docs.github.com/copilot/concepts/agents/github-copilot-app
 [getting-started]: https://docs.github.com/copilot/how-tos/github-copilot-app/getting-started
 [customize]: https://docs.github.com/copilot/how-tos/github-copilot-app/customize-github-copilot-app