ci-cd-pipeline-authoring

# CI/CD Pipeline Authoring ## Overview TaskTrooper does not run your build — it **reads your GitHub Actions workflows** and maps their jobs and files onto its own pipeline. A task moved to `ready_for_qa` runs your `validate`/`build`/`test` jobs; `trigger_release` dispatches your production deploy workflow. If your workflows are not named the way the detector expects, the pipeline silently skips them and QA/release stalls. **Core principle:** The workflow you author is the contract with the platform. Name jobs and files with the keywords the detector matches, or the stage does not exist as far as TaskTrooper is concerned. ## Two kinds of pipeline slot **Status slots** (mapped to a *job name* in any workflow) — read for pass/fail at `ready_for_qa`: | Slot | Job name must contain (by repo kind) | |------|--------------------------------------| | `validate` | `lint`, `vet`, `staticcheck` (backend/worker) · `lint`, `tsc`, `typecheck` (frontend) · `lint`, `swiftlint`, `analyze` (mobile) | | `build` | `build`, `compile`, `docker` (backend/worker/frontend) · `build`, `xcodebuild`, `archive`, `fastlane` (mobile) | | `test` | `test`, `vitest`, `jest` | A mobile `build` job must **not** contain `docker` (excluded). Give each job a clear `name:` — the detector matches the job's display name. **Deploy slots** (mapped to a *workflow file*) — dispatched, one workflow file per slot: | Slot | Workflow `name:` / file must contain | |------|--------------------------------------| | `st...