Skip to content

[workshop-diagrams] Add theme-aware explanatory diagram for standard vs. agentic workflow classification - #3552

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
diagram/side-quest-05-02-classify-flow-b888e77d056f9905
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
diagram/side-quest-05-02-classify-flow-b888e77d056f9905

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

Adds a new theme-aware explanatory diagram to workshop/side-quest-05-02-aw-deep-dive.md, the "Classify Agentic vs. Standard Workflows" side quest. This is a new concept diagram, not a migration — the file had no existing images.

What it shows

A single trigger (on: pull_request) forking into two paths:

  1. Standard workflow — fixed deterministic steps (Run tests → Fail on non-zero → Upload coverage) that always produce the same result.
  2. Agentic workflow — the agent reads live context, makes a judgment call, and posts output that varies each run (Read issues → Judge & group → Post summary).

Files added

  • workshop/images/side-quest-05-02-classify-flow-light.svg
  • workshop/images/side-quest-05-02-classify-flow-dark.svg

Why this helps learners

The side quest asks learners to classify four tasks as standard vs. agentic vs. hybrid, but the core distinction was only explained in prose. This diagram gives learners a visual anchor for the "same trigger, different path" mental model before they start classifying, making the key signal (fixed steps vs. judgment calls) easier to recall.

QA performed

  • Ran scripts/check-svg-visual-language.js against both new SVGs — no violations.
  • Served the repo locally and used Playwright to render the <picture> block under light and dark prefers-color-scheme, confirming currentSrc resolves to -light.svg and -dark.svg respectively.
  • Visually inspected both renders — all labels stay inside their boxes, no clipping or overlap.

Warning

Firewall blocked 6 domains

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

  • accounts.google.com
  • android.clients.google.com
  • clients2.google.com
  • registry.npmjs.org
  • www.google.com
  • www.gstatic.com

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

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "registry.npmjs.org"
    - "www.google.com"
    - "www.gstatic.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · copilot · auto · 98.8 AIC · ⌖ 16.5 AIC · ⊞ 10.4K · ◷

  • expires on Sep 20, 2026, 2:39 AM UTC

… classification

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor Author

This pull request was automatically closed because it expired on 2026-09-20T02:39:07.663Z.

Closed by Workflow

@github-actions github-actions Bot closed this Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants