Rename CI job to checks with a stable display name

[mjdavidson]

Follow-up from the pre-public audit: the CI job was keyed test but runs no tests (it runs lint, format check, and typecheck). This renames the key to checks and pins an explicit display name CI, decoupling the branch ruleset's required-check context from the YAML key so future job-key renames can't silently break merge requirements.

Paired change (applied on the ruleset side alongside this PR): the Main branch protection ruleset's required status check context changes test → CI.

---

Devin shepherd: https://app.devin.ai/sessions/53aea6d91c084725a3f62734cbc26a43

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Greptile Summary

This PR updates the GitHub Actions CI job naming. The main changes are:

• Renames the workflow job key from test to checks.
• Adds an explicit job display name of CI.
• Keeps the existing install, lint, format check, and typecheck steps unchanged.

Confidence Score: 5/5

Safe to merge with minimal risk.

The change is limited to a GitHub Actions job identifier and explicit display name while preserving the existing workflow steps.

No files require special attention.

T-Rex Logs

What T-Rex did

• T-Rex ran the requested general contract validation and noted that local artifact references were not uploaded.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
.github/workflows/ci.yml	Renames the CI job key to checks and adds a stable displayed job name CI; no issues found.

_{Reviews (1): Last reviewed commit: "Rename CI job: checks with stable displa..." | Re-trigger Greptile}

[devin-ai-integration]

Thanks @greptile-apps — confirmed. The change is scoped to the CI job identifier (test → checks) plus the explicit name: CI display name; all workflow steps (install, lint, format check, typecheck) are unchanged. The name: CI is intentional and load-bearing: it's the ruleset's required-status-check context, decoupled from the YAML job key. No further changes needed.

[greptile-apps]

Acknowledged — thanks for the confirmation. The rename makes sense as a quality-of-life improvement: decoupling the ruleset's required-check context from the YAML job key means future job-key renames won't silently break branch protection. The name: CI being the stable anchor for the ruleset is a good pattern. Nothing further to flag here.