Add scenario steps files, update scripts and docs for injection model

Co-authored-by: GeekTrainer <6109729+GeekTrainer@users.noreply.github.com>

Author: Copilot

docs/authoring/new-scenario-guide.md

@@ -33,7 +33,7 @@ Skipped exercises are listed in `scenario.yml` and are omitted when the workshop
 
 ## Step 2 — Create the scaffolding
 
-Run the scaffolding script from the repository root:
+Use the scaffolding script to get started:
 
 ```bash
 python scripts/new-scenario.py <scenario-id>
@@ -47,8 +47,8 @@ The script creates:
 scenarios/
   <scenario-id>/
     scenario.yml          ← pre-filled template; edit this next
-    overrides/
-      README.md           ← placeholder for exercise overrides
+    steps/
+      README.md           ← placeholder for exercise steps files
 ```
 
 ---
@@ -120,39 +120,53 @@ Add each exercise to be skipped to the `skip` list in `scenario.yml`.
 
 ---
 
-## Step 5 — Write exercise overrides (as needed)
+## Step 5 — Write exercise steps files (as needed)
 
-Each exercise in `workshop-content/` contains a `## Scenario` section that describes the task in the context of Tailspin Toys. You will need to override this section for any exercise where the Tailspin-specific context does not make sense for your application.
+The core exercises in `workshop-content/` are generic templates. Each contains a `## Scenario` section and other sections describing tasks in application-neutral language. When your scenario needs scenario-specific content — your company name, tech-stack details, feature descriptions — create a steps file.
 
-Create the override file at:
+A steps file lives at:
 
 ```
-scenarios/<scenario-id>/overrides/<exercise-filename>.md
+scenarios/<scenario-id>/steps/<exercise-filename>.md
 ```
 
-The override file should be a **complete exercise file** structured identically to the original in `workshop-content/`, with the `## Scenario` section rewritten for your application and any Tailspin-specific references replaced.
+It contains **only the `## ` sections that differ from the core**. When exercises are rendered for your scenario, each matching section in the steps file replaces its counterpart in the core exercise. Sections not present in the steps file are taken unchanged from the core.
 
 > [!TIP]
-> Start by copying the original exercise file, then search for "Tailspin" and replace every occurrence with your scenario's equivalent. Update code snippets and prompts to match your tech stack.
+> Only include the sections that genuinely differ. If only `## Scenario` needs to change, your steps file only needs that one section.
 
-### Minimal override example
+### Minimal steps file example
 
-If only the `## Scenario` section needs to change:
+If only the `## Scenario` section needs to change for exercise 1:
 
 ```markdown
-<!-- scenarios/my-scenario/overrides/1-mcp.md -->
-
-# Exercise 1 - Setting up the backlog with Copilot agent mode and GitHub's MCP Server
-
-...same content as workshop-content/1-mcp.md, except:...
-
 ## Scenario
 
 You are a developer for <Company Name> — <company_description>. You've been
 assigned tasks to introduce new functionality. To file your backlog of issues
 you'll enlist the help of Copilot Chat in agent mode and the GitHub MCP server.
+```
+
+### Multi-section steps file example
+
+If exercises 3 needs a custom scenario description and application startup instructions:
+
+```markdown
+## Scenario
+
+As the list of <primary_entities> grows, <company_name> wants to allow users
+to filter by <filter_feature>. With the help of Copilot Agent Mode you'll add
+the new feature!
+
+## Running the application
+
+The <company_name> application is a <company_description>. It has two main
+components: a frontend written in <frontend_language> and a backend written
+in <backend_language>.
+
+### Starting the application
 
-...rest of file unchanged...
+...your tech-stack-specific startup steps here...
 ```
 
 ---
@@ -169,8 +183,8 @@ The script checks:
 
 - All required fields are present in `scenario.yml`.
 - Every exercise listed in `skip` exists in `workshop-content/`.
-- Every override file in `overrides/` corresponds to an exercise in `workshop-content/`.
-- No override exists for an exercise in the `skip` list (that would be a conflict).
+- Every steps file in `steps/` corresponds to an exercise in `workshop-content/`.
+- No steps file exists for an exercise in the `skip` list (that would be a conflict).
 
 Fix any issues reported before continuing.
 
@@ -220,7 +234,7 @@ Use this checklist to track your progress:
 - [ ] Created scaffolding with `scripts/new-scenario.py`
 - [ ] Completed all fields in `scenario.yml`
 - [ ] Identified exercises to skip
-- [ ] Written overrides for exercises with Tailspin-specific content
+- [ ] Written steps files for exercises with scenario-specific content
 - [ ] Validated with `scripts/validate-scenario.py` (zero errors)
 - [ ] Updated `scenarios/README.md` table
 - [ ] Tested the scenario end-to-end

rendered/tailspin-toys-dotnet/0-prereqs.md

@@ -0,0 +1,47 @@
+# Exercise 0: Prerequisites
+
+Before you get started on the lab, there's a few tasks you need to complete to get everything ready. You need to get a copy of the repository which includes the code, then spin up a [codespace][codespaces] to use to create your code.
+
+## Setting up the Lab Repository
+
+To create a copy of the repository for the code you'll create an instance from the [template][template-repository]. The new instance will contain all of the necessary files for the lab, and you'll use it as you work through the exercises. 
+
+1. In a new browser window, navigate to the GitHub repository for this lab: `https://github.com/github-samples/agents-in-sdlc`.
+2. Create your own copy of the repository by selecting the **Use this template** button on the lab repository page. Then select **Create a new repository**.
+
+    ![Use this template button](images/ex0-use-template.png)
+
+3. If you are completing the workshop as part of an event being led by GitHub or Microsoft, follow the instructions provided by the mentors. Otherwise, you can create the new repository in an organization where you have access to Copilot coding agent and can assign issues to Copilot.
+
+    ![Input the repository template settings](images/ex0-repository-settings.png)
+
+4. Make a note of the repository path you created (**organization-or-user-name/repository-name**), as you will be referring to this later in the lab.
+
+## Creating a codespace
+
+Next up, you'll be using a codespace to complete the lab exercises. [GitHub Codespaces][codespaces] are a cloud-based development environment that allows you to write, run, and debug code directly in your browser. It provides a fully-featured IDE with support for multiple programming languages, extensions, and tools.
+
+1. Navigate to your newly created repository.
+2. Select the green **Code** button.
+
+    ![Select the Code button](images/ex0-code-button.png)
+
+3. Select the **Codespaces** tab and select the **+** button to create a new Codespace.
+
+    ![Create a new codespace](images/ex0-create-codespace.png)
+
+The creation of the codespace will take several minutes, although it's still far quicker than having to manually install all the services! That said, you can use this time to explore other features of GitHub Copilot, which we'll turn your attention to next!
+
+> [!IMPORTANT]
+> You'll return to the codespace in a future exercise. For the time being, leave it open in a tab in your browser.
+
+## Summary
+
+Congratulations, you have created a copy of the lab repository! You also began the creation process of your codespace, which you'll use when you begin writing code.
+
+## Next step
+
+Let's explore how you can use Model Context Protocol (MCP) to interact with external services! You can do this by [setting up the backlog with Copilot agent mode and GitHub's MCP Server](./1-mcp.md).
+
+[codespaces]: https://github.com/features/codespaces
+[template-repository]: https://docs.github.com/repositories/creating-and-managing-repositories/creating-a-template-repository