fix: curriculum sequencing audit - 10 issues resolved

- Move Step 1.5 (Git identity) after Step 6 (Install Git) in pre-workshop setup
- Eliminate dual section/step numbering in pre-workshop setup TOC and headings
- Add merge conflicts mini-lesson to Day 1 Block 5 before contribution sprint
- Add fork-and-clone instructions to Day 2 Block 1 (was assumed but never taught)
- Fix duplicate Part 6B labels in Day 1 Block 6 (now 6A through 6F)
- Fix insiders-a11y-tracker prerequisite (Issue Templates is Day 2, not Day 1)
- Add 15-minute Copilot orientation to start of Day 2 Block 2
- Standardize agent count to six across DAY1_AGENDA and DAY2_AGENDA
- Add note mapping Chapters 14-15 to Day 2 agenda blocks in course guide
- Fix Day 2 intro merge conflict claim (replaced with accurate Day 1 summary)
- Update external anchor references in chapters 04, 05, and appendix B
- Rebuild all HTML output

Author: accesswatch

DAY1_AGENDA.md

@@ -1,7 +1,7 @@
 # Day 2 Agenda
 ## From Contributor to Product Maker - Igniting the Forge
 
-> **The premise of Day 2:** You spent Day 1 learning how GitHub works - by hand, in the browser, with your screen reader. You filed real issues. You opened a real pull request. You resolved a real merge conflict. Those skills are yours now.
+> **The premise of Day 2:** You spent Day 1 learning how GitHub works - by hand, in the browser, with your screen reader. You filed real issues. You opened a real pull request. You reviewed someone else's work. Those skills are yours now.
 >
 > Day 2 is about what you can build with those skills. You will deepen your contributions using VS Code and GitHub Copilot. You will use Accessibility Agents - a live, public accessibility project built by your facilitator - not as a shortcut around the skills you learned, but as a **product you can understand, evaluate, critique, and improve** because you now know exactly what it is doing and why.
 >
@@ -83,18 +83,35 @@ VS Code has a dedicated screen reader accessibility mode that adjusts verbosity,
 
 **Key setting to check:** Open Settings (`Ctrl+,`) → search `accessibility support` → confirm it shows `on`.
 
-### Step 2 - Open Accessibility Agents as a Workspace
-1. Open a terminal (`Ctrl+Backtick`)
-2. Navigate to wherever you cloned your fork: `cd path/to/accessibility-agents`
-3. Open VS Code in that folder: `code .`
-4. VS Code opens with the `accessibility-agents` repository as your workspace
+### Step 2 - Fork, Clone, and Open Accessibility Agents
+
+Before you can work on Accessibility Agents locally, you need your own copy (a fork) and a local clone of that fork.
+
+**Fork the repository (browser - a Day 1 skill):**
+1. Navigate to [github.com/community-access/accessibility-agents](https://github.com/community-access/accessibility-agents)
+2. Find and activate the **Fork** button (`B` to navigate buttons)
+3. Keep the defaults and activate **Create fork**
+4. GitHub redirects you to your fork: `github.com/[your-username]/accessibility-agents`
+
+**Clone the fork (VS Code terminal - your first Git command):**
+1. Open a terminal in VS Code (`Ctrl+Backtick`)
+2. Navigate to where you want to store projects: `cd ~/Documents` (or your preferred folder)
+3. Clone your fork:
+   ```bash
+   git clone https://github.com/[your-username]/accessibility-agents.git
+   ```
+4. Enter the project folder: `cd accessibility-agents`
+5. Open VS Code in that folder: `code .`
+6. VS Code opens with the `accessibility-agents` repository as your workspace
+
+> **Screen reader note:** The `git clone` command prints progress messages. When you hear the terminal go quiet, it is done. The folder now exists on your machine.
 
 **What to navigate first (with screen reader):**
 
 | VS Code Area | Key | What You Hear |
 |-------------|-----|---------------|
 | Explorer sidebar | `Ctrl+Shift+E` | File and folder tree |
-| `.github/agents/` folder | `Arrow keys` | Five `.agent.md` files |
+| `.github/agents/` folder | `Arrow keys` | Six `.agent.md` files |
 | `.github/prompts/` folder | `Arrow keys` | 28 slash command template files |
 | `Documentation/` folder | `Arrow keys` | `GETTING-STARTED.md`, `GUIDE.md` |
 | `ai-instructions/` folder | `Arrow keys` | Copilot, Claude, OpenAI integration guides |
@@ -124,6 +141,25 @@ Press `Ctrl+Shift+I` to open the Chat panel.
 ## Block 2 - Deep Contribution with Copilot
 **10:45-12:00**
 
+### Copilot Orientation (15 min)
+
+Before diving into contributions, get familiar with how Copilot works as a writing partner.
+
+**Inline suggestions (`Ctrl+I`):**
+1. Open any `.md` file in the workspace
+2. Place your cursor at the end of a line and press `Ctrl+I`
+3. Type a prompt: `Add a sentence explaining why this agent uses heading navigation`
+4. Copilot suggests text inline. Press `Tab` to accept, `Escape` to dismiss
+5. **Screen reader note:** NVDA announces "Inline suggestion" when one appears. Press `Alt+]` to read the suggestion before accepting
+
+**Chat as a thinking partner:**
+1. Open Chat (`Ctrl+Shift+I`) if not already open
+2. Type: `Explain what the daily-briefing agent does in plain English`
+3. Read the response. Use `H` (heading navigation) to jump between sections
+4. Try: `What are three ways I could improve this agent for screen reader users?`
+
+**Key principle:** Copilot drafts. You decide. Every suggestion should be read, evaluated, and edited before committing. Your name goes on the commit.
+
 ### Purpose
 Make a richer contribution to your fork of `accessibility-agents` using Copilot as a writing partner - not a replacement for your judgment. Copilot helps you articulate ideas you already have. The idea - the product intention - is yours.
 
@@ -182,7 +218,7 @@ Agents are run in a specific sequence - from broadest to most specific, from obs
 | 1 | `@daily-briefing` | Reading your notification inbox and activity summary | [Navigating Repos](docs/02-navigating-repositories.md) + [Notifications](docs/09-notifications.md) |
 | 2 | `@issue-tracker` | Triaging and prioritizing issues manually | [Working with Issues](docs/04-working-with-issues.md) + [Labels & Milestones](docs/08-labels-milestones-projects.md) |
 | 3 | `@pr-review` | Manually reviewing a PR diff and writing inline comments | [Working with Pull Requests](docs/05-working-with-pull-requests.md) |
-| 4 | `@insiders-a11y-tracker` | Filing accessibility bugs and applying WCAG labels | [Working with Issues](docs/04-working-with-issues.md) + [Issue Templates](docs/15-issue-templates.md) |
+| 4 | `@insiders-a11y-tracker` | Filing accessibility bugs and applying WCAG labels | [Working with Issues](docs/04-working-with-issues.md) + [Labels & Milestones](docs/08-labels-milestones-projects.md) |
 
 `@analytics` is available as an extension if Block 3 runs ahead of schedule - it requires understanding contribution graphs and activity history.
 

DAY2_AGENDA.md

@@ -9,22 +9,22 @@
 
 ## Table of Contents
 
-1. [What You Will Need](#1-what-you-will-need)
-2. [Step 1 - Create Your GitHub Account](#2-step-1--create-your-github-account)
-3. [Step 1.5 - Configure Git Identity (If Using Git Locally)](#3-step-15--configure-git-identity-if-using-git-locally)
-4. [Step 2 - Configure GitHub Accessibility Settings](#4-step-2--configure-github-accessibility-settings)
-5. [Step 3 - Configure Your Profile](#5-step-3--configure-your-profile)
-6. [Step 4 - Verify Modern GitHub Interface](#6-step-4--verify-modern-github-interface)
-7. [Step 5 - Test Your Screen Reader on GitHub](#7-step-5--test-your-screen-reader-on-github)
-8. [Step 6 - Install Git and Visual Studio Code](#8-step-6--install-git-and-visual-studio-code-day-2)
-9. [Step 7 - Install GitHub Copilot in VS Code](#9-step-7--install-github-copilot-in-vs-code-day-2)
-10. [Step 8 - Verification Checklist](#10-step-8--verification-checklist)
-11. [Other GitHub Access Methods (Reference Only)](#11-other-github-access-methods-reference-only)
-12. [Getting Help Before the Event](#12-getting-help-before-the-event)
+1. [What You Will Need](#what-you-will-need)
+2. [Step 1 - Create Your GitHub Account](#step-1-create-your-github-account)
+3. [Step 2 - Configure GitHub Accessibility Settings](#step-2-configure-github-accessibility-settings)
+4. [Step 3 - Configure Your Profile](#step-3-configure-your-profile)
+5. [Step 4 - Check GitHub Feature Preview Settings](#step-4-check-github-feature-preview-settings)
+6. [Step 5 - Set Up Your Screen Reader and Browser](#step-5-set-up-your-screen-reader-browser)
+7. [Step 6 - Install Git and Visual Studio Code](#step-6-install-git-and-visual-studio-code)
+8. [Step 7 - Configure Git Identity](#step-7-configure-git-identity)
+9. [Step 8 - Install VS Code Extensions](#step-8-install-vs-code-extensions)
+10. [Step 9 - Verification Checklist](#step-9-verification-checklist)
+11. [Other GitHub Access Methods (Reference Only)](#other-github-access-methods-reference-only)
+12. [Getting Help Before the Event](#getting-help-before-the-event)
 
 ---
 
-## 1. What You Will Need
+## What You Will Need
 
 ### Hardware
 - A computer running Windows or macOS
@@ -59,9 +59,9 @@ You only need **one** of these. Use whichever you are most comfortable with.
 
 ---
 
-## 2. Step 1 - Create Your GitHub Account
+## Step 1 - Create Your GitHub Account
 
-If you already have a GitHub account, skip to [Step 2](#4-step-2--configure-github-accessibility-settings).
+If you already have a GitHub account, skip to [Step 2](#step-2-configure-github-accessibility-settings).
 
 > **Before you begin:** Have your email address and a chosen password ready. The signup form is a single-page form with several fields - your screen reader will encounter a verification puzzle partway through (see note below).
 
@@ -182,66 +182,7 @@ Copy-ready paragraph for `CONTRIBUTING.md` / registration forms
 
 ---
 
-## 3. Step 1.5 - Configure Git Identity (If Using Git Locally)
-
-> **Important:** Complete this step after installing Git (Step 6) and before the workshop begins. Git must know who you are before you can make your first commit.
-
-Git needs to know who you are so every commit you make is attributed to you. This affects how your name appears in project history.
-
-### Configure in VS Code (Recommended for This Workshop)
-
-1. Open **Visual Studio Code**
-2. Open the integrated terminal:
-   - Menu: **Terminal → New Terminal**
-   - Keyboard: `` Ctrl+` `` (Windows) or `` Cmd+` `` (Mac)
-3. Type the following commands, replacing with your information:
-
-```bash
-git config --global user.name "Your Name"
-git config --global user.email "your-email@example.com"
-```
-
-**What to use:**
-- **user.name:** Your real name or the name you want shown on commits (e.g., "Jane Smith")
-- **user.email:** The email address associated with your GitHub account (must match exactly)
-
-**Screen reader note:** The terminal in VS Code is accessible with all major screen readers. Press `` Ctrl+` `` to move focus to the terminal, type your commands, and press `Enter`.
-
-### Why This Matters
-
-Every commit you make includes:
-- Your name
-- Your email address  
-- A timestamp
-- The commit message
-
-If Git isn't configured, it will either:
-- Use a default name like "Unknown" (looks unprofessional in project history)
-- Refuse to create commits with an error message
-
-### Verify Your Configuration
-
-Run this command to see your current settings:
-
-```bash
-git config --global --list
-```
-
-You should see:
-```
-user.name=Your Name
-user.email=your-email@example.com
-```
-
-### Using the Correct Email
-
-Use the same email you registered with GitHub. If you're concerned about privacy, GitHub offers a no-reply email you can use: `username@users.noreply.github.com` - find it in [Settings → Emails](https://github.com/settings/emails).
-
-**When to configure this:** Before your first commit in VS Code. You can skip it on Day 1 if you're only working through the GitHub web interface.
-
----
-
-## 4. Step 2 - Configure GitHub Accessibility Settings
+## Step 2 - Configure GitHub Accessibility Settings
 
 These settings make GitHub significantly more usable with a screen reader. **Do not skip this section** - one setting in particular (hovercards) adds significant noise to every page if left on.
 
@@ -347,7 +288,7 @@ Theme is on a separate page: [GitHub Appearance Settings](https://github.com/set
 
 ---
 
-## 5. Step 3 - Configure Your Profile
+## Step 3 - Configure Your Profile
 
 Your GitHub profile is your public identity in the open source community. Setting it up properly helps maintainers know who you are.
 
@@ -372,7 +313,7 @@ A profile picture humanizes your contributions. It can be a photo or any image.
 
 ---
 
-## 6. Step 4 - Check GitHub Feature Preview Settings
+## Step 4 - Check GitHub Feature Preview Settings
 
 GitHub continuously rolls out improvements to its interface. Some enhancements start as opt-in Feature Previews before becoming the standard experience. Two features matter most for screen reader users working through this workshop:
 
@@ -450,7 +391,7 @@ If you open Feature Preview and neither **"New Issues Experience"** nor **"New F
 
 ---
 
-## 7. Step 5 - Set Up Your Screen Reader & Browser
+## Step 5 - Set Up Your Screen Reader & Browser
 
 ### NVDA (Windows)
 
@@ -522,7 +463,7 @@ If you open Feature Preview and neither **"New Issues Experience"** nor **"New F
 
 ---
 
-## 8. Step 6 - Install Git and Visual Studio Code
+## Step 6 - Install Git and Visual Studio Code
 
 ### Install Git First
 
@@ -550,7 +491,7 @@ Git is often already present via Xcode Command Line Tools. To check:
 - PowerShell is accessible with all screen readers via Browse Mode or Forms Mode
 - Type `git --version`, press `Enter`, then press `↑` to re-read the output line
 
-Once Git is installed, proceed to [Step 1.5](#3-step-15--configure-git-identity-if-using-git-locally) to configure your name and email before your first commit.
+Once Git is installed, you will configure your Git identity in Step 7 after VS Code is set up.
 
 ---
 
@@ -612,7 +553,56 @@ If VS Code did **not** prompt you automatically, enable it manually:
 
 ---
 
-## 9. Step 7 - Install VS Code Extensions
+## Step 7 - Configure Git Identity
+
+Now that Git is installed, tell it who you are. Git embeds your name and email in every commit you make, and this affects how your contributions appear in project history.
+
+### Configure in VS Code
+
+1. Open **Visual Studio Code**
+2. Open the integrated terminal:
+   - Menu: **Terminal → New Terminal**
+   - Keyboard: `` Ctrl+` `` (Windows) or `` Cmd+` `` (Mac)
+3. Type the following commands, replacing with your information:
+
+```bash
+git config --global user.name "Your Name"
+git config --global user.email "your-email@example.com"
+```
+
+**What to use:**
+- **user.name:** Your real name or the name you want shown on commits (e.g., "Jane Smith")
+- **user.email:** The email address associated with your GitHub account (must match exactly)
+
+**Screen reader note:** The terminal in VS Code is accessible with all major screen readers. Press `` Ctrl+` `` to move focus to the terminal, type your commands, and press `Enter`.
+
+### Why This Matters
+
+If Git isn't configured, it will either:
+- Use a default name like "Unknown" (looks unprofessional in project history)
+- Refuse to create commits with an error message
+
+### Verify Your Configuration
+
+Run this command to see your current settings:
+
+```bash
+git config --global --list
+```
+
+You should see:
+```
+user.name=Your Name
+user.email=your-email@example.com
+```
+
+### Using the Correct Email
+
+Use the same email you registered with GitHub. If you're concerned about privacy, GitHub offers a no-reply email you can use: `username@users.noreply.github.com` - find it in [Settings → Emails](https://github.com/settings/emails).
+
+---
+
+## Step 8 - Install VS Code Extensions
 
 This workshop uses two VS Code extensions. Both are published by GitHub and are free. Install them in the order shown below.
 
@@ -703,7 +693,7 @@ For this workshop, Free tier is sufficient. If you want unlimited access, paid p
 
 ---
 
-## 10. Step 8 - Verification Checklist
+## Step 9 - Verification Checklist
 
 Work through this checklist before Day 1. Check off each item:
 
@@ -742,7 +732,7 @@ GIT & VS CODE (required before the workshop)
 
 ---
 
-## 11. Other GitHub Access Methods (Reference Only)
+## Other GitHub Access Methods (Reference Only)
 
 This workshop focuses entirely on GitHub.com in the browser and VS Code. However, you should be aware that other ways to work with GitHub exist. We list them here for your reference - we will not be teaching these in depth.
 
@@ -799,7 +789,7 @@ We are not covering Git commands in this workshop. If you want to learn Git, the
 
 ---
 
-## 12. Getting Help Before the Event
+## Getting Help Before the Event
 
 If you cannot complete any step in this guide before the workshop: