Problem statement
workshop/07-your-first-workflow.md maps to the highest-dropout step in the current simulation (07-first-workflow, 22.1% conditional dropout among 22,633 at-risk runs, 95% MC interval 21.6%–22.7%). Investigation traced part of this to a simulator-model artifact: the commit/push instructions for daily-report-status.lock.yml (lines 105–110) are far enough (>500 characters) from the literal string .lock.yml that the lexical workflowLockPublishCueCount cue-detector scored 0 for this step, even though the checkpoint at line 121 explicitly requires both files pushed to main. We supplied a semantic evaluation to correct the simulator, but the underlying page structure — where the compile command, the commit/push commands, and the file-name confirmation are spread across three separate blocks (lines 97–101, 105–110, 115–123) — is a genuine, if secondary, path-clarity risk for real learners, and the real, unmodeled failure category at this step is copilot-access-missing (4,051 of the simulated failures), reflecting genuine model-access friction that the page defers to a linked troubleshooting step.
Proposed change
Add a single-line inline confirmation immediately after the git push command block (after line 110) that explicitly names both files being pushed, e.g.: "This pushes both daily-report-status.md and daily-report-status.lock.yml to main." This closes the path-clarity gap for learners (and for any future automated content assessment) without changing the compile/commit/push sequence, removing steps, or altering the Copilot-access verification flow that already exists at lines 23–42.
Failure mode classification
Access barrier — the dominant recorded failure category (copilot-access-missing, 4,051 failures) is model/auth access friction; the secondary workflow-authoring-friction (952 failures) is partly a path-clarity issue addressed by this change. Neither reflects a conceptual/scaffolding gap.
Quantitative guardrail
- Current
overall_score for 07-your-first-workflow.md: 6.25/10
- Current dimension scores:
active_learning 6.3/10, checkpoint_quality 0.0/10 (instrumentation bug tracked separately), scaffolding 5.0/10, cognitive_load and readability unaffected by this change
- Current Learning KPI index for this step: 3.65/10 (
(2.0×6.3 + 2.0×0.0 + 1.5×5.0)/5.5)
- The proposed change adds one clarifying sentence with no new concepts, no removed practice steps, and no change to the existing checklist — it should leave
overall_score and the Learning KPI index flat or slightly improved (via a marginal scaffolding/clarity gain), and must not reduce the existing hands-on compile/commit/push practice.
Acceptance criteria
Suggested owner profile
workshop maintainer
Related to #3132
Generated by 🔬 Workshop Student Simulator · copilot · auto · 219.4 AIC · ⌖ 10.3 AIC · ⊞ 15.2K · ◷
Problem statement
workshop/07-your-first-workflow.mdmaps to the highest-dropout step in the current simulation (07-first-workflow, 22.1% conditional dropout among 22,633 at-risk runs, 95% MC interval 21.6%–22.7%). Investigation traced part of this to a simulator-model artifact: the commit/push instructions fordaily-report-status.lock.yml(lines 105–110) are far enough (>500 characters) from the literal string.lock.ymlthat the lexicalworkflowLockPublishCueCountcue-detector scored 0 for this step, even though the checkpoint at line 121 explicitly requires both files pushed tomain. We supplied a semantic evaluation to correct the simulator, but the underlying page structure — where the compile command, the commit/push commands, and the file-name confirmation are spread across three separate blocks (lines 97–101, 105–110, 115–123) — is a genuine, if secondary, path-clarity risk for real learners, and the real, unmodeled failure category at this step iscopilot-access-missing(4,051 of the simulated failures), reflecting genuine model-access friction that the page defers to a linked troubleshooting step.Proposed change
Add a single-line inline confirmation immediately after the
git pushcommand block (after line 110) that explicitly names both files being pushed, e.g.: "This pushes bothdaily-report-status.mdanddaily-report-status.lock.ymltomain." This closes the path-clarity gap for learners (and for any future automated content assessment) without changing the compile/commit/push sequence, removing steps, or altering the Copilot-access verification flow that already exists at lines 23–42.Failure mode classification
Access barrier — the dominant recorded failure category (
copilot-access-missing, 4,051 failures) is model/auth access friction; the secondaryworkflow-authoring-friction(952 failures) is partly a path-clarity issue addressed by this change. Neither reflects a conceptual/scaffolding gap.Quantitative guardrail
overall_scorefor07-your-first-workflow.md: 6.25/10active_learning6.3/10,checkpoint_quality0.0/10 (instrumentation bug tracked separately),scaffolding5.0/10,cognitive_loadandreadabilityunaffected by this change(2.0×6.3 + 2.0×0.0 + 1.5×5.0)/5.5)overall_scoreand the Learning KPI index flat or slightly improved (via a marginalscaffolding/clarity gain), and must not reduce the existing hands-on compile/commit/push practice.Acceptance criteria
overall_scorefor07-your-first-workflow.mdstays flat or improves after the change(2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5) stays flat or improvesnpx --yes markdownlint-cli2 "**/*.md") with no new errorsSuggested owner profile
workshop maintainerRelated to #3132