chore(ci): remove dead Codecov upload steps + lock pins

[hyperpolymath]

Removed CI references to apps that are no longer installed on this account/org.

Why this is a fix, not a tidy-up

• Codecov was uninstalled as a GitHub App, but its action steps remain in workflows.
• The estate Actions allowlist already pruned codecov/codecov-action@* (standards/config/settings/actions-allowlist.json -> pruned_from_live_2026_09_02), so a workflow still calling it fails at job start instead of quietly no-op-ing.
• Snyk / Codacy / Mergify / ImgBot / CodeFactor are on the estate never-re-add list (standards spec §9, rulings R1/R4/R5).

Changes

• .github/workflows/actions.lock — applied
• .github/workflows/elixir-ci.yml — applied
• .github/workflows/rust-ci.yml — applied

Notes

• actions.lock entries for the removed actions are deleted in this same commit (the same-PR regen rule in the CI/CD regularisation spec §6.4), so actions-lock-verify sees no drift.
• Removals are line-exact; no other line was reformatted and no comment was re-wrapped.
• Historical records (milestone logs, CHANGELOG, audit docs, specs) that describe the removal were deliberately left untouched.
• The gitar-approved label is intentionally frozen per docs/LABELS.adoc — it is not an active Gitar install, so it stays.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 9b17b9d7-f574-4da8-8479-f145b735ee82

📥 Commits

Reviewing files that changed from the base of the PR and between 82e3e9b and 809a594.

⛔ Files ignored due to path filters (1)

• .github/workflows/actions.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• .github/workflows/elixir-ci.yml
• .github/workflows/rust-ci.yml

💤 Files with no reviewable changes (2)

• .github/workflows/rust-ci.yml
• .github/workflows/elixir-ci.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Coverage reports are no longer uploaded to Codecov for Elixir and Rust CI workflows.
  • Existing coverage report generation and minimum-coverage checks remain unchanged.

Walkthrough

The Elixir and Rust CI coverage jobs no longer upload reports to Codecov. The Elixir job also loses its custom display name. Existing report generation and Rust coverage enforcement remain.

Changes

Coverage workflow cleanup

Layer / File(s)	Summary
Remove Codecov uploads .github/workflows/elixir-ci.yml, .github/workflows/rust-ci.yml	The Elixir and Rust coverage jobs no longer run the Codecov upload action. The Elixir job also uses its default display name. Rust report generation and the 60% line-coverage check remain.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main changes: removal of obsolete Codecov upload steps and lock pins from CI.
Description check	✅ Passed	The description directly explains the removal of obsolete CI references, the affected workflows, the lock updates, and the reason for the change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the coverage trail
Codecov steps now leave no veil
Elixir keeps its work in line
Rust still guards the sixty sign
CI hops onward, neat and bright}

_{Comment @coderabbitai help to get the list of available commands.}