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

• nesy/.github/workflows/ci.yml — applied
• zotpress/.github/workflows/test.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: df230943-b960-4724-bb04-574b583ff9cf

📥 Commits

Reviewing files that changed from the base of the PR and between 8daf101 and f0eb7df.

📒 Files selected for processing (2)

• nesy/.github/workflows/ci.yml
• zotpress/.github/workflows/test.yml

💤 Files with no reviewable changes (2)

• nesy/.github/workflows/ci.yml
• zotpress/.github/workflows/test.yml

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

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: Analyze (actions)

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Coverage reports are no longer uploaded to Codecov during JavaScript and PHP automated test workflows.

Walkthrough

The Node.js and PHP GitHub Actions workflows no longer upload coverage reports to Codecov. All other workflow behaviour remains unchanged.

Changes

Coverage upload removal

Layer / File(s)	Summary
Workflow coverage upload removal .github/workflows/ci.yml, .github/workflows/test.yml	The test workflows no longer run their conditional Codecov upload steps for Node.js and PHP coverage files.

Priority: ⬇️ Low

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

Change: Bug fix

Suggested reviewers: metadatastician

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the removal of obsolete Codecov CI steps and lock pins.
Description check	✅ Passed	The description directly explains the removed Codecov steps, related lock entries, and the reason for the changes.
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 hops through workflows bright
Coverage files stay out of flight
Codecov steps are now still
Tests continue by their will
Neat YAML rests beneath moonlight}

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud