Summary
Investigate the stale failed CodeQL setup run and either restore a working CodeQL workflow or document that CodeQL is intentionally not used for this Swift package.
Why this is useful
The repo has a visible failed CodeQL setup run and no current successful security analysis run in the recent action list. Cleaning this up would make the repository health signal clearer for a public CLI/daemon project.
Proposed small change
- Check whether a CodeQL workflow should exist for the Swift package.
- If yes, add or fix the workflow so it runs successfully on pushes/PRs or a schedule.
- If no, remove stale setup expectations and document the preferred security/static-analysis check instead.
Evidence checked
gh run list shows a completed failure named CodeQL Setup from 2026-05-23..github/workflows/codeql.yml was not present via the repository contents API.- The open issue list contains a Windows daemon service parity issue, not this CI/status cleanup.
Validation gate
Stitch should not work on this until Adrien explicitly approves this issue or asks Stitch to implement it.
Suggested acceptance check
- The Actions tab no longer presents CodeQL as a stale failed setup, or the repository has a documented alternative security check.
Summary
Investigate the stale failed CodeQL setup run and either restore a working CodeQL workflow or document that CodeQL is intentionally not used for this Swift package.
Why this is useful
The repo has a visible failed CodeQL setup run and no current successful security analysis run in the recent action list. Cleaning this up would make the repository health signal clearer for a public CLI/daemon project.
Proposed small change
Evidence checked
gh run listshows a completed failure namedCodeQL Setupfrom 2026-05-23..github/workflows/codeql.ymlwas not present via the repository contents API.Validation gate
Stitch should not work on this until Adrien explicitly approves this issue or asks Stitch to implement it.
Suggested acceptance check