fix: return gh-aw coverage controller to manual canary - #924
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Repository UI (inherited), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
Agent Completion Truth Gate: NOT_APPLICABLEEvidence agrees. Machine-readable verdict{
"details": {},
"reasons": [],
"verdict": "not_applicable"
} |
There was a problem hiding this comment.
Pull request overview
Returns the coverage controller to a safe, manual-only canary.
Changes:
- Removes the scheduled trigger and regenerates the gh-aw lock.
- Clarifies Codex/Jules responsibilities.
- Prevents test-module import poisoning.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/focused-coverage-controller.md |
Makes the controller manual-only. |
.github/workflows/focused-coverage-controller.lock.yml |
Regenerates the compiled workflow. |
tests/test_skills_integration.py |
Removes harmful module stubs and adds regression coverage. |
Outcome
Contain the unsafe post-merge activation from #921 without disabling Jules or removing gh-aw.
Progresses #898 and focused issue #920.
Why this PR exists
PR #921 merged externally while its own description said Do not merge and its exact-head gh-aw validation was red. The failure was not an application failure: gh-aw v0.82.14 compiled all three workflows, then detected a nondeterministic lock change caused by the shorthand
schedule: daily.This is the single canonical post-merge correction for #920. It does not create a competing implementation.
Changes
workflow_dispatchso the real gh-aw canary remains installed and testable.v0.82.14.Local exact-source verification
gh aw compile focused-coverage-controller --validate --approve: 0 errors, 0 warnings.gh aw compile focused-coverage-controller --zizmor --poutine --approve: 0 errors, 0 warnings.git diff --check: passed.Safety / activation