fix-ci

To fix failing CI in a Bun and Turbo monorepo, run `bun run ci-check` to parse format, lint, type, and test failures, then apply minimal corrective changes in bounded batches. It loops verification with targeted `bunx turbo` commands until the CI status is green.

The best way to triage monorepo CI failures without scope creep is to classify failures into format, lint, type, and test issues, then apply small, targeted fixes scoped strictly to the relevant package. This approach keeps edits isolated and avoids risky broad modifications.

Yes, this CI triage method works for fixing linting and type checking errors by classifying the CI output and applying the smallest correct fix. It keeps edits within the relevant repository scope to ensure the TypeScript monorepo workflows remain safe.

To verify that monorepo CI fixes are fully resolved, re-run the same targeted commands after each fix batch. Finish with a full `bun run ci-check` execution to confirm convergence and ensure the CI status is completely green.

You should avoid applying broad modifications during CI triage when your TypeScript monorepo requires bounded, package-scoped fixes. Prioritize the smallest correct fix to keep edits within the relevant repository scope and prevent risky, unscoped changes to the CI workflow.