birdcc-cicdlisted

# BIRD CI/CD Generate workflows from the current `setup-birdcc` composite-action contract. Do not assume the action installs a global `birdcc` command. ## Invariants 1. `setup-birdcc` checks out the repository by default. Do not add a duplicate `actions/checkout` step unless setting `checkout: "false"` on the action. 2. A config-only repository should set `install-dependencies: "false"` and `cache-turbo: "false"`, then run `@birdcc/cli` ephemerally. 3. A pnpm project that declares `@birdcc/cli` should use its lockfile and `pnpm exec birdcc`. 4. There is no `cache-pnpm` input. With dependency installation enabled, the action caches the pnpm store automatically. `cache-turbo` controls only `.turbo`. 5. Pass `${{ steps.<id>.outputs.bird-bin }}` as `BIRD_BIN` for `birdcc lint --bird`. 6. Never embed routing secrets in workflow YAML, command arguments, artifacts, annotations, or uploaded configs. ## Workflow 1. Inspect the repository package manager, lockfile, existing checkout, project config, entry points, BIRD major version, and whether production configs are submodules. 2. Choose one of the patterns in [`references/setup-birdcc.md`](references/setup-birdcc.md): - config-only + ephemeral CLI; - locked pnpm dependency; - BIRD 2/3 matrix; - changed-file or submodule workflow. 3. Use the currently published `@v1.0.0` release for a normal workflow. Do not emit `@v1` unless that major tag is verified to exist. For protected production repositori