CI/CD pipeline stages infographic in dark-mode tech diagram

Tech architecture infographic titled "CI/CD Pipeline Stages" using HOW-IT-WORKS archetype, designed for a mid-level developer audience. Show a clear numbered stage flow with labeled boxes connected by directional arrows across a modern software delivery lifecycle. Include these canonical English-tech components as visual boxes: Developer Browser / IDE, Git Repository, Webhook API, CI Orchestrator, Build Runner, Artifact Registry, Test Suite, Security Scanner, Container Builder, Deployment Queue, CD Controller, Staging Environment, Approval Gate, Production Environment, Monitoring Dashboard, Metadata DB, Cache, Message Queue, Generic Cloud Infrastructure. Every box must contain: a simple tech icon, the component name, and a one-line English role description. Example role descriptions: "Writes code and opens pull requests", "Stores source and branch history", "Receives push events and triggers pipeline", "Coordinates pipeline jobs and status", "Executes build and test steps", "Stores versioned build outputs", "Runs unit and integration checks", "Checks dependencies and image issues", "Builds deployable container image", "Buffers deployment tasks", "Applies release workflow to environments", "Validates release in pre-production", "Requires human approval for promotion", "Runs live application version", "Shows health, logs, and metrics", "Stores pipeline state and run metadata", "Caches dependencies for faster jobs", "Transports asynchronous job events", "Hosts generic compute and networking resources". Use arrows with short English labels showing what crosses between components, technically accurate where relevant: "git push", "Webhook HTTPS POST", "Pipeline config", "Job request", "Source checkout", "Dependency cache", "Build artifact", "Test results", "Scan report", "Container image", "Enqueue deploy job", "Release manifest", "Approval decision", "Deploy status", "Health metrics", "Run metadata", "Queue event". Structure the infographic as a left-to-right or top-to-bottom numbered workflow: 1 Source Commit, 2 Trigger Pipeline, 3 Build Application, 4 Run Automated Tests, 5 Scan and Package, 6 Deploy to Staging, 7 Approve and Release to Production. Add a numbered legend (1-7) in English explaining the lifecycle: 1. Developer commits code and pushes changes to the Git repository. 2. A webhook API receives the event over HTTPS and starts the CI pipeline. 3. The CI orchestrator assigns jobs to build runners, which fetch source code and use cache when available. 4. Automated test suites validate code quality and return pass or fail results. 5. Security scanning and packaging produce a versioned artifact or container image in the registry. 6. The CD controller deploys the release to staging, records metadata, and waits for approval if required. 7. After approval, the controller promotes the release to production and monitoring reports runtime health. Include supporting infra boxes for DB, cache, and queue explicitly labeled as Metadata DB, Dependency Cache, and Deployment Queue. Make the layout read as a true tech architecture infographic, not a project timeline, not a Gantt chart, and not a network topology sketch; emphasize lifecycle stages, system handoffs, and artifact movement. Visual style: editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use dark-mode developer aesthetics with a dark charcoal or near-black background, neon cyan, neon blue, neon purple, and neon green accents, subtle glow edges, crisp grid alignment, high contrast labels, polished modern engineering mood. Add small badges or captions for outputs like "Artifact v1.2.3", "Exit code 0", "HTTP 200 webhook received", "Deployment succeeded" where appropriate, but avoid any security-claim overstatements and do not present it as an audited reference architecture. Use only generic cloud icons, generic repository icons, generic container and server symbols, no real cloud-vendor logos. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).