ci: validate .env.example by copying it before test runs

[antonio-gg-dev]

Related #

make test loads .env via the Makefile, but CI test workflows were not creating that file from .env.example. That meant a syntax error in .env.example could go unnoticed in GitHub Actions while still breaking local test runs for contributors following the setup documented in CONTRIBUTING.md.

Changes

• Fixed the malformed BASHUNIT_COVERAGE_THRESHOLD_HIGH entry in .env.example by separating the assignment from the inline comment so Bash can parse it correctly.
• Updated the test workflows to copy .env.example to .env before running the suite, so CI now exercises the same configuration path used locally.
• This prevents regressions where .env.example drifts into an invalid Bash file without being caught by automated checks.

Checklist

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

[github-actions]

✅ Contributor Report

User: @antonio-gg-dev
Status: Passed (12/13 metrics passed)

Metric	Description	Value	Threshold	Status
PR Merge Rate	PRs merged vs closed	100%	>= 30%	✅
Repo Quality	Repos with ≥100 stars	1	>= 0	✅
Positive Reactions	Positive reactions received	83	>= 1	✅
Negative Reactions	Negative reactions received	3	<= 5	✅
Account Age	GitHub account age	3894 days	>= 30 days	✅
Activity Consistency	Regular activity over time	100%	>= 0%	✅
Issue Engagement	Issues with community engagement	0	>= 0	✅
Code Reviews	Code reviews given to others	6	>= 0	✅
Merger Diversity	Unique maintainers who merged PRs	1	>= 2	❌
Repo History Merge Rate	Merge rate in this repo	100%	>= 0%	✅
Repo History Min PRs	Previous PRs in this repo	4	>= 0	✅
Profile Completeness	Profile richness (bio, followers)	70	>= 0	✅
Suspicious Patterns	Spam-like activity detection	0	N/A	✅

---

_{Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-03-30 to 2026-03-30}