| name | ci-canary |
| description | Inspect or exercise the CI baseline and ordered transient canary workflows. |
Intent
Use this skill for CI-baseline and hardware-canary checks, especially when verifying that the repository still follows the intended safe deployment order.
Inputs
- Whether the user wants dry-run validation, workflow review, or local canary execution.
Execution
- Use the workflow files under
.github/workflows/ as the source of truth for CI behavior.
- For local canary validation, prefer
bash tools/run_ordered_transient_canary.sh --dry-run --skip-build unless the user explicitly wants a live run.
- Keep the sequencing explicit:
u64 first, c64u.ue2 second, transient-only.
Validation
- Confirm that baseline artifacts and canary ordering still match the documented model.
- Call out any regression that would introduce a persistent flash path into the canary.
Safety
- Never substitute
kickburn for the transient canary path.