Live CI Snapshot on the Engineering Hub
Most portfolio case studies show a pipeline diagram someone drew once and never updated. Mine ships a JSON snapshot from Woodpecker on every green main deploy. The engineering hub fetches it at runtime so the Security → Build → Deploy → Notify flow matches what .woodpecker.yml actually runs today.
The Discord and Plane article covers what happens when CI fails. This one covers what visitors see when it succeeds — a live map of how the site got there.
scripts/generate-pipeline-snapshot.cjs parses step ids from .woodpecker.yml and collapses them into four flow nodes: Security (Gitleaks, Trivy, DefectDojo, gate), Build + QA, Deploy, and Notify. It writes public/ci/pipeline-snapshot.json with repository URLs, Woodpecker links, and optional in-CI status when Woodpecker env vars are present.