[side-quest] Extract pre-flight diagnostics into optional side quest

[github-actions]

Caution

Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: README.md

What changed

Mined workshop/08-run-your-workflow.md for a self-contained detour: the "Pre-flight check" section was a two-part diagnostic checklist (lock file freshness + billing configuration match) embedded inside the main "trigger and watch your run" step.

Side quest extracted: workshop/side-quest-08-02-preflight-diagnostics.md — a focused walkthrough of the two checks that catch the leading causes of model-access-not-configured failures before a learner clicks Run.

Routing update for learners:

• 08-run-your-workflow.md now has a short summary of the pre-flight idea, an Optional Side Quest callout (matching the existing <details> pattern used elsewhere in the workshop, e.g. Step 9) linking to the new side quest, and a condensed inline self-check so the main path still works standalone without requiring the detour.
• The new side quest ends with a return link back to Run and Watch Your Workflow (Step 8).
• workshop/README.md lists the new side quest in the existing "Optional Side Quests" section, noting it branches from Step 8.

No YAML frontmatter snippets were introduced (the side quest only contains illustrative bash commands), so no gh aw compile --validate step was needed.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by 🗺️ Side Quest · copilot · auto · 152.4 AIC · ⌖ 15 AIC · ⊞ 7.2K · ◷

• expires on Sep 25, 2026, 1:56 PM UTC

[github-actions]

Protected files were modified in this pull request and require manual scrutiny before merge.

Please verify that each protected-file change is intentional, policy-compliant, and safe:

• Protected files: README.md