ci-workflowlisted

# CI workflow Generate GitHub Actions workflow files for CI pipelines. Enforce parallel job execution, emoji job naming, and gated deployment stages. ## Guards - A request for what runs inside a deploy, publish, or release job stops at the gate. Credentials, environments, and deploy targets are invisible to this skill, so emit the job with its `needs` wiring and a placeholder step, then name what the caller fills in. Never guess a deploy command. - The build, test, and deploy commands belong to the project. Read them from its scripts rather than asserting a second copy in the workflow. ## Workflow setup - Include `workflow_dispatch` on every workflow alongside the primary trigger. - Pin all actions to major version tags (`@v4`, never `@latest` or `@main`). - Use `runs-on: ubuntu-latest` for all jobs. ## Job naming - Name jobs with emoji + title: `🛡️ Checks`, `🛡️ Static Checks`, `🧪 Unit Tests`, `📦 Build Check`, `🎭 E2E Tests`, `🚀 Deploy`, `🔍 Code Quality`, `🏷️ Release`, `🔒 Security`. ## Job granularity - Start a new pipeline with the checks that share setup in one job: static analysis, unit tests, and build. A project with no run history has nothing to measure, and one job is the shape that costs least to reverse. - Keep them in one job while the gate runs under roughly two minutes end to end. Each extra job repays checkout, dependency install, and toolchain setup before it reaches a stage, so a split at that duration costs more than the parallelism returns. -