Add CI validation for coverage badge accuracy

[Copilot]

CI now validates that the coverage badge in badges/coverage.svg matches actual test coverage. PRs with stale badges will fail CI and be unmergeable.

Changes

• Added script/check-coverage-badge.ts: Extracts coverage from coverage-summary.json and badges/coverage.svg, fails if they don't match
• Updated ci-test script: Now runs npx tsx script/check-coverage-badge.ts after tests complete
• Updated copilot instructions: Added coverage badge section requiring agents update the badge before committing code changes

Usage

# Validate coverage badge
npx tsx script/check-coverage-badge.ts

# Update coverage badge after code changes
npm run coverage

The ci-test script automatically validates badge accuracy, ensuring all PRs maintain an accurate coverage badge.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• check.trivy.dev
  • Triggering command: /usr/bin/trivy trivy filesystem --config /action/lib/.automation/trivy.yaml /tmp/lint eval{setpgrp};ev4 CREATE_LOG_FILE=--xargs inter-worker-res--results /release sh /bin/grep date +%F �� (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Update ci-test to include checking coverage and ensuring that the coverage badge is up to date.

If run in an actions workflow and the coverage badge is incorrect it should fail.

Update the copilot instructions to ensure that it will ensure the coverage badge is accurate before making a commit that includes any code change. Remind the agent that there is a check in ci that will make the PR unmergeable if the coverage badge is inaccurae.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[eriksw]

@copilot Your previous commit introduced lint failures because the super-linter was not run despite markdown files being changed. Why exactly was the super-linter not run?

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• check.trivy.dev
  • Triggering command: /usr/bin/trivy trivy filesystem --config /action/lib/.automation/trivy.yaml /tmp/lint se JUPYTER_NBQA_MYPY "false" exit 255; gitleaks directory --no-banner --redact --config /action/lib/.automation/.gitleaks.tom10101 perl ARGV s.md /tmp/lint/.10101 /bin/date sleep l ARGV date leep on/.gitleaks.tomperl (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)