Move PR reviewer workflow to step 14b (after next-steps reflection step) (#1931)

* Initial plan

* feat: move PR reviewer workflow to step 14b (after next-steps)

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

.github/skills/micro-environment-simulator/workshop-student-journey.js

@@ -52,8 +52,8 @@ const STEP_FILE_ALIASES = {
   "08b-interpret-your-run": ["08b-interpret-your-run.md"],
   "09-agentic-editing": ["09-agentic-editing.md"],
   "12-test-and-iterate": ["12-test-and-iterate.md"],
-  "13-pr-reviewer-workflow": ["13-pr-reviewer-workflow.md"],
   "14-next-steps": ["14-next-steps.md"],
+  "14b-pr-reviewer-workflow": ["14b-pr-reviewer-workflow.md"],
   "15-conditional-logic": ["15-conditional-logic.md"],
   "16-connect-data-source": ["16-connect-data-source.md"],
   "17-add-mcp-tools": ["17-add-mcp-tools.md"],
@@ -82,8 +82,8 @@ const STEP_IDS = [
   "08b-interpret-your-run",
   "09-agentic-editing",
   "12-test-and-iterate",
-  "13-pr-reviewer-workflow",
   "14-next-steps",
+  "14b-pr-reviewer-workflow",
   "15-conditional-logic",
   "16-connect-data-source",
   "17-add-mcp-tools",
@@ -911,6 +911,31 @@ function buildTransitions() {
       return { ok: true, state: applyLearning(next, context, { troubleshooting: 0.08, agentic: 0.05 }) };
     },
     "14-next-steps": (state, context) => ({ ok: true, state: applyLearning(state, context, { confidence: 0.01 }) }),
+    "14b-pr-reviewer-workflow": (state, context) => {
+      const compiledWorkflowCheck = ensureCompiledWorkflow(
+        state,
+        "workflow-not-compiled",
+        "Compile the scenario workflow with `gh aw compile`, then commit and push the generated `.lock.yml`, or use a CCA session that compiles and commits the edited workflow before trying the PR reviewer step."
+      );
+      if (!compiledWorkflowCheck.ok) return compiledWorkflowCheck;
+      const ccaGuidanceCheck = ensure(
+        !needsCcaPromptGuidance(state, context) || hasCcaPromptGuidance(state, context),
+        "The PR reviewer step does not clearly tell CCA learners to invoke `/agentic-workflows` or show the browser-only compile path.",
+        "copilot-skill-guidance-missing",
+        "Add `/agentic-workflows` skill invocation guidance and a UI-only compile path to the PR reviewer workflow step."
+      );
+      if (!ccaGuidanceCheck.ok) return ccaGuidanceCheck;
+      const readiness = contentReadinessCheck(state, context, {
+        salt: 223,
+        category: "event-trigger-friction",
+        failedAssumption: "The learner understands scheduled triggers but struggles to adapt to an event-driven `pull_request` trigger and the required `safe-outputs` limit.",
+        remediation: "Keep the event trigger contrast with scheduled workflows prominent and add a worked example of `safe-outputs: create-issue-comment: limit: 1`.",
+        emphasis: { bias: 0.1, conceptWeight: 0.1, complexityWeight: 0.08 }
+      });
+      if (!readiness.ok) return readiness;
+      const next = updateWorkflowCompileState(state, context, { allowCloudAgent: true });
+      return { ok: true, state: applyLearning(next, context, { agentic: 0.08, actions: 0.04, troubleshooting: 0.03 }) };
+    },
     "15-conditional-logic": (state, context) =>
       advancedLessonStep(state, context, {
         requiresRun: true,

workshop/12-test-and-iterate.md

@@ -95,5 +95,5 @@ If you want a stricter review loop, score each run for accuracy, completeness, a
 - [ ] I compared the new run with the previous run and decided what to change next
 
 <!-- journey: all -->
-**Next:** [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md)
+**Next:** [What's Next? Keep Exploring](14-next-steps.md)
 <!-- /journey -->

workshop/14-next-steps.md

@@ -75,7 +75,11 @@ Here's a quick recap of the concepts you've touched. The diagram below shows how
 - [ ] You drafted a two-sentence brief for your next agentic workflow
 - [ ] You know where to find the gh-aw docs when you need them
 
-You've reached the end of the main path — but the graph stays open. Come back any time, branch off in a new direction, and keep building. 🚀
+You've reached the end of the scheduled-workflow path — but there is one more step on the main track before you head into advanced territory. Come back to explore any of the deeper topics when you're ready.
 
 <!-- /journey -->
 
+<!-- journey: all -->
+**Next:** [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md)
+<!-- /journey -->
+

workshop/13-pr-reviewer-workflow.md workshop/14b-pr-reviewer-workflow.mdworkshop/13-pr-reviewer-workflow.md renamed to workshop/14b-pr-reviewer-workflow.md

@@ -122,7 +122,7 @@ Then recompile, push, and update the PR branch to trigger another run.
 - [ ] I can explain why `safe-outputs: create-issue-comment: limit: 1` matters for an event-driven workflow
 
 <!-- journey: all -->
-**Next:** [What's Next? Keep Exploring](14-next-steps.md)
+**Next:** [Make Your Workflow Smarter with Conditional Logic](15-conditional-logic.md)
 <!-- /journey -->
 
 ---

workshop/README.md

@@ -26,8 +26,8 @@ A hands-on workshop that takes you from zero to a fully automated, AI-powered wo
 | 8b | [Interpret Your First Run](08b-interpret-your-run.md) |
 | 9 | [Refine Your Workflow with Agentic Editing](09-agentic-editing.md) |
 | 12 | [Test and Improve Your Workflow](12-test-and-iterate.md) |
-| 13 | [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md) |
 | 14 | [What's Next? Keep Exploring](14-next-steps.md) |
+| 14b | [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md) |
 
 ## Curriculum — Part 2: Go Deeper
 
@@ -53,18 +53,18 @@ A hands-on workshop that takes you from zero to a fully automated, AI-powered wo
 - [Terminal Basics](side-quest-01-01-terminal-basics.md) — optional primer that branches from [Step 1](01-prerequisites.md).
 - [Environment Reference](side-quest-01-02-environment-reference.md) — glossary of workshop environments and tool terms with official docs links; branches from [Step 1](01-prerequisites.md).
 - [Install `gh-aw` Troubleshooting](side-quest-06-01-install-troubleshooting.md) — optional install troubleshooting reference that branches from [Step 6](06-install-gh-aw.md).
-- [Using `gh aw compile` to Catch Errors Early](side-quest-07-01-compile-workflow.md) — quick reference for `gh aw compile`, `--validate`, `--watch`, and common compile errors; branches from [Step 7](07-your-first-workflow.md), [Step 11a](07-your-first-workflow.md), or [Step 13](12-test-and-iterate.md).
+- [Using `gh aw compile` to Catch Errors Early](side-quest-07-01-compile-workflow.md) — quick reference for `gh aw compile`, `--validate`, `--watch`, and common compile errors; branches from [Step 7](07-your-first-workflow.md), [Step 11a](07-your-first-workflow.md), or [Step 12](12-test-and-iterate.md).
 - [Fix Codespaces `actions:write` Errors When Running `gh aw run`](side-quest-08-01-codespaces-actions-write.md) — troubleshooting guide for Codespaces workflow-trigger permission errors with a UI-first path and advanced recovery path; branches from [Step 8](08-run-your-workflow.md).
 - [Diagnosing Common Agent Output Patterns](side-quest-09-01-debug-output.md) — expanded troubleshooting guide for the five most common log patterns; branches from [Step 9](08b-interpret-your-run.md).
 - [Writing a Clear Agent Brief](side-quest-10-01-agent-brief.md) — five-step framework for designing any agentic workflow brief; branches from [Step 10](09-agentic-editing.md).
 - [Jailbreaking the Agent Brief](side-quest-10-02-jailbreak-brief.md) — explains how adversarial instructions embedded in repository content attempt to override the agent's task brief, and how the compiled brief, minimal `permissions:`, `safe-outputs`, and `network.allowed-domains` contain any partial success; branches from [Step 10](09-agentic-editing.md).
 - [Frontmatter Deep Dive — Part A](side-quest-11-01-frontmatter-deep-dive.md) — walkthrough of the opening, trigger, and permissions sections of `gh-aw` frontmatter, with predict-and-try activities; branches from [Step 11a](07-your-first-workflow.md).
 - [Frontmatter Deep Dive — Part B](side-quest-11-08-frontmatter-tools-outputs.md) — walkthrough of the tools, safe-outputs, closing fence, and agent body sections, with predict-and-try activities; continues from Part A.
-- [Pattern: Auto-Label PRs by Content](side-quest-13-01-pr-labeler-pattern.md) — apply labels automatically based on which files changed in a pull request; branches from [Step 13](13-pr-reviewer-workflow.md).
-- [Pattern: Generate a PR Summary Comment](side-quest-13-02-pr-summary-pattern.md) — post a structured, changelog-ready summary comment when a pull request opens; branches from [Step 13](13-pr-reviewer-workflow.md).
-- [Pattern: PR Review Checklist](side-quest-13-03-pr-checklist-pattern.md) — evaluate pull requests against a quality checklist and post a pass/fail table; branches from [Step 13](13-pr-reviewer-workflow.md).
-- [Observe and Reduce Token Costs](side-quest-13-04-token-optimization.md) — hands-on optimization activity for building an AIC baseline, auditing expensive runs, identifying cost drivers, and testing one token-reduction change at a time; branches from [Step 13](13-pr-reviewer-workflow.md).
-- [Fuzzy Schedule Expressions](side-quest-13-01-schedule-expressions.md) — quick reference for choosing between `daily`, `hourly`, `weekly`, and other fuzzy schedule expressions; branches from [Step 13](12-test-and-iterate.md).
+- [Pattern: Auto-Label PRs by Content](side-quest-13-01-pr-labeler-pattern.md) — apply labels automatically based on which files changed in a pull request; branches from [Step 14b](14b-pr-reviewer-workflow.md).
+- [Pattern: Generate a PR Summary Comment](side-quest-13-02-pr-summary-pattern.md) — post a structured, changelog-ready summary comment when a pull request opens; branches from [Step 14b](14b-pr-reviewer-workflow.md).
+- [Pattern: PR Review Checklist](side-quest-13-03-pr-checklist-pattern.md) — evaluate pull requests against a quality checklist and post a pass/fail table; branches from [Step 14b](14b-pr-reviewer-workflow.md).
+- [Observe and Reduce Token Costs](side-quest-13-04-token-optimization.md) — hands-on optimization activity for building an AIC baseline, auditing expensive runs, identifying cost drivers, and testing one token-reduction change at a time; branches from [Step 14b](14b-pr-reviewer-workflow.md).
+- [Fuzzy Schedule Expressions](side-quest-13-01-schedule-expressions.md) — quick reference for choosing between `daily`, `hourly`, `weekly`, and other fuzzy schedule expressions; branches from [Step 12](12-test-and-iterate.md).
 - [Evaluating and Iterating on Agent Output](side-quest-12-01-iterate-agent-output.md) — structured rubric for judging output quality, a five-row problem-to-fix reference table, and a one-change-at-a-time iteration loop; branches from [Step 12](12-test-and-iterate.md).
 - [GitHub Actions Expressions and Contexts](side-quest-15-01-expressions-and-contexts.md) — deep dive into `${{ }}` syntax, available context objects, output references, and `if:` conditions; branches from [Step 15](15-conditional-logic.md).
 - [YAML Frontmatter Pitfalls](side-quest-11-02-yaml-frontmatter.md) — reference guide for the five most common YAML mistakes; branches from [Step 11a](07-your-first-workflow.md).

workshop/side-quest-13-01-pr-labeler-pattern.md

@@ -8,7 +8,7 @@ Extend your PR reviewer workflow to automatically apply GitHub labels based on t
 
 ## Before You Start
 
-- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md).
+- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md).
 - Your practice repository has at least one label already created. If not, go to **Issues → Labels** in your repository and create labels like `documentation`, `tests`, and `bug-fix`.
 
 ## Why Auto-Labelling?

workshop/side-quest-13-02-pr-summary-pattern.md

@@ -8,7 +8,7 @@ Build a PR summary workflow that posts a structured, human-readable summary comm
 
 ## Before You Start
 
-- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md).
+- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md).
 
 ## Why a Structured Summary?
 

workshop/side-quest-13-03-pr-checklist-pattern.md

@@ -8,7 +8,7 @@ Build a workflow that evaluates every new pull request against a short review ch
 
 ## Before You Start
 
-- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md).
+- Complete [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md).
 
 ## Why a Checklist Workflow?
 

workshop/side-quest-13-04-token-optimization.md

@@ -6,7 +6,7 @@
 
 ## 📋 Before You Start
 
-- You completed [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md).
+- You completed [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md).
 - You have a working PR reviewer workflow or another workflow with at least 5 completed runs so you can compare before-and-after usage.
 - If you want extra background on AIC, audit artifacts, or budget guardrails, continue later to [Audit and Monitor Your Agentic Workflows](25-audit-and-observability.md) and [Manage Costs and AI Credit Budgets](26-manage-costs-and-budgets.md).
 
@@ -157,5 +157,5 @@ Paste the relevant excerpt from your `gh aw audit --parse` output below the prom
 - [ ] You can name the next optimization you would test if cost is still too high
 
 <!-- journey: all -->
-Return to [Build Your First Event-Driven Workflow: PR Auto-Reviewer](13-pr-reviewer-workflow.md).
+Return to [Build Your First Event-Driven Workflow: PR Auto-Reviewer](14b-pr-reviewer-workflow.md).
 <!-- /journey -->