Add VS Code terminal guidance and classic-vs-agentic comparison table to Steps 5–7 and 11 (#201)

Author: Copilot

workshop/05-agentic-workflows-intro.md

@@ -26,10 +26,11 @@ If you're coming from classic GitHub Actions, this table shows exactly where the
 
 | Dimension | Classic GitHub Actions | Agentic Workflow |
 |---|---|---|
-| **File format** | `.yml` YAML | `.md` Markdown (YAML frontmatter + task brief) |
+| **File format** | `.github/workflows/*.yml` | `.github/workflows/*.md` (compiled to `.lock.yml`) |
 | **Task description** | Shell commands and scripts in `steps:` | Natural language instructions below the frontmatter |
 | **Execution** | Deterministic — same input always gives same output | AI agent interprets the brief and decides how to act at runtime |
 | **Handles ambiguity** | Fails or needs explicit branching logic | Reasons through ambiguous inputs and adapts |
+| **Runtime** | No AI model involved | Copilot or another LLM is the runtime |
 | **Best for** | CI/CD pipelines, builds, deployments | Summaries, triage, reporting, and tasks that need judgment |
 
 > [!NOTE]

workshop/06-install-gh-aw.md

@@ -22,6 +22,13 @@ extension so you can compile and run agentic workflows from your terminal.
 
 ## Steps
 
+> [!TIP]
+> **Using VS Code?** Open the integrated terminal with `` Ctrl+` `` (macOS: `` Cmd+` ``),
+> then run all `gh aw` commands there. If a command is unfamiliar, try:
+> `gh copilot suggest "how do I install a gh extension"`
+
+Before you can install the extension, verify the GitHub CLI is set up correctly:
+
 > [!IMPORTANT]
 > **Run these pre-flight checks before installing `gh-aw`.**
 >

workshop/07-your-first-workflow.md

@@ -23,6 +23,11 @@ You'll create a simple agentic workflow file in your repository using the `gh-aw
 
 ## Steps
 
+> [!TIP]
+> **Using VS Code?** Open the integrated terminal with `` Ctrl+` `` (macOS: `` Cmd+` ``),
+> then run all `gh aw` commands there. If a command is unfamiliar, try:
+> `gh copilot suggest "how do I install a gh extension"`
+
 ### 1. Create the workflows directory
 
 Agentic workflow files live alongside regular GitHub Actions workflows inside `.github/workflows/`.

workshop/11-build-daily-status.md

@@ -26,6 +26,11 @@ An agentic workflow file has two parts: **frontmatter** (YAML between `---` fenc
 | Tools | `tools:` | Enables the GitHub MCP tool via `gh-proxy`, scoped to the permissions above. |
 | Write guardrail | `safe-outputs:` | The only write actions the agent may take — here, one issue comment per run. |
 
+> [!NOTE]
+> Reminder: if you're confused about why this file ends in `.md` instead of `.yml`, see the [Classic vs. Agentic comparison table in Step 5](05-agentic-workflows-intro.md#side-by-side-classic-actions-vs-agentic-workflows).
+
+Before diving in, there is an optional side quest if you want more detail first:
+
 > [!TIP]
 > **Optional Side Quest:** Want a section-by-section explanation of every key with tables and examples before you build? See [Side Quest: Frontmatter Deep Dive](side-quest-frontmatter-deep-dive.md). It's fully optional — everything you need to complete this step is in the build sections below.