ci-cd-and-automation

Define ordered quality gates: lint, static analysis, unit tests, build, integration tests, and security audit. Use the workflow YAML templates in references/ci-templates.md for basic CI, then enable branch protection so failed checks block merging.

Apply optimizations in order of impact: cache Gradle dependencies with setup-java, split lint/test/build into parallel jobs, use path filters to skip unrelated jobs, shard tests with matrix builds, and move slow tests off the critical path.

Yes. Copy the CI failure output and give it to the agent with instructions to fix and verify locally. Lint failures map to running lint tasks, type errors to fixing the flagged location, and test failures to a debugging workflow.

No. CI should use separate test secrets stored in GitHub Secrets or a vault. Production secrets belong in the deployment platform. Commit only .env.example templates and never store secrets in code or CI config files.

Use staged rollouts: auto-deploy to staging, verify manually, then promote to production with a 15-minute error monitoring window. Keep a manual rollback workflow dispatch ready, and use feature flags to disable risky features without redeploying.