[workshop-diagrams] Add theme-aware explanatory diagram for classic Actions vs agentic workflow

[github-actions]

Summary

This PR migrates the existing single-theme 00-actions-vs-agentic.svg to a light/dark SVG pair and uses it in the workshop.

What changed

• Workshop file: workshop/05-agentic-workflows-intro.md — added a <picture> block near Activity 2 ("agentic or standard?") to anchor the diagram in context
• New SVGs added:
  • workshop/images/00-actions-vs-agentic-light.svg — light palette (background #f6f8fa, panels white)
  • workshop/images/00-actions-vs-agentic-dark.svg — dark palette (background #0d1117, panels #161b22)

Migration vs new concept

This is a migration of an existing explanatory diagram that was present in the repo but not referenced by any Markdown file. No new concept was invented; the geometry, labels, and content are preserved from the original. A dark-theme variant was created with fully adapted colors (blue triggers, yellow task brief, red danger chips, green safe-outputs, purple agent box, dark-adapted VS badge).

Why it helps learners

The side-by-side comparison of Classic GitHub Actions YAML versus an Agentic Workflow is the most important mental model shift in the entire workshop. Placing it visually right before Activity 2 gives learners a concrete reference frame before they classify tasks as agentic or standard, reinforcing the key differences (static steps vs. AI agent judgment, no safety guardrails vs. sandbox + integrity filter + safe outputs).

QA

Both SVGs were rendered via Playwright with Firefox:

• Light: currentSrc ends with -light.svg ✅, 109 KB non-blank render ✅
• Dark: currentSrc ends with -dark.svg ✅, 109 KB non-blank render ✅
• Markdownlint: 0 issues ✅

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• awmgmcpg
• storage.googleapis.com

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

network:
  allowed:
    - defaults
    - "awmgmcpg"
    - "storage.googleapis.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · 78.5 AIC · ⌖ 10.4 AIC · ⊞ 6.4K · ◷

• expires on Jul 30, 2026, 6:29 PM UTC

[github-actions]

Warning

Firewall blocked 1 domain

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

• awmgmcpg

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

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by ✅ AW Accuracy PR Reviewer for #2336 · 58.1 AIC · ⌖ 5.01 AIC · ⊞ 4.3K

[github-actions]

Inaccuracy: write-summary is not a valid safe-output surface name.

The diagram shows safe-outputs: write-summary, but write-summary does not exist as a gh-aw safe-output surface. Valid surface names include add-comment, create-issue, create-pull-request, create-pull-request-review-comment, update-release, etc. (see safe-outputs reference).

For a daily report workflow, add-comment is a realistic surface to illustrate.

Suggested fix: replace safe-outputs: write-summary with safe-outputs: add-comment.

[github-actions]

Inaccuracy: gh-proxy is a mode value, not a top-level tool name.

The diagram shows tools: gh-proxy, which implies gh-proxy is a tool identifier. In gh-aw frontmatter, gh-proxy is the value of the mode field under the github toolset — it is not a standalone tool name. The correct frontmatter form is:

tools:
  github:
    mode: gh-proxy
    toolsets: [repos]

Suggested fix: change the label to tools: github (gh-proxy mode) or simply tools: github to avoid implying gh-proxy is a tool name.

[github-actions]

Inaccuracy: write-summary is not a valid safe-output surface name.

Same issue as the light variant: write-summary does not exist as a gh-aw safe-output surface. Valid surfaces include add-comment, create-issue, create-pull-request, etc. (see safe-outputs reference).

Suggested fix: replace safe-outputs: write-summary with safe-outputs: add-comment.

[github-actions]

Inaccuracy: gh-proxy is a mode value, not a top-level tool name.

Same issue as the light variant: tools: gh-proxy misrepresents the frontmatter structure. In gh-aw, gh-proxy is the value of the mode field under the github toolset, not a standalone tool identifier.

Suggested fix: change the label to tools: github (gh-proxy mode) or simply tools: github.