test: add e2e pipeline integration tests; raise coverage floor to 80% (#93, #35, #97, #66)

[Liohtml]

Fourth batch of repo-health fixes, focused on testing and deployment defaults:

• [repo-health] Medium: Integration test suite is empty — zero integration tests committed #93 – New integration suite (tests/integration/test_pipeline_e2e.py) runs the real WorkflowEngine over synthetic DICOM studies through ingest → preprocess → report: directory source, ZIP source, de-identified report (no PHI strings in output), and German HTML report. No network and no optional ML dependencies required.
• [repo-health] Low: 55% test coverage floor is too low for a medical-grade imaging tool #35 / progress on Increase test coverage from 60% to 80% #17 – Coverage floor raised from 55 % to 80 % in pyproject.toml and CI (--cov-fail-under=80); actual coverage is 86 %.
• [repo-health] Low: --dob CLI flag accepted and stored but explicitly not verified — creates false sense of access control #97 – --dob help text now states explicitly that the value is stored as a credential but NOT verified by MedCheck.
• [repo-health] Medium: Default Docker deployment binds 0.0.0.0 without requiring MEDCHECK_API_KEY — API is publicly unauthenticated #66 – docker-compose.yml publishes port 8080 on 127.0.0.1 only by default, with a comment explaining that network exposure requires changing the mapping AND setting MEDCHECK_API_KEY.

Closes #93, closes #35, closes #97, closes #66.

🤖 Generated with Claude Code

https://claude.ai/code/session_014ywk8AWq5mgbeERmvuhcJy

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@Liohtml, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4cda8585-14e7-4713-8254-3afbf3bd42ae

📥 Commits

Reviewing files that changed from the base of the PR and between c0f42d5 and 33cf82a.

📒 Files selected for processing (5)

• .github/workflows/ci.yml
• docker-compose.yml
• pyproject.toml
• src/medcheck/main.py
• tests/integration/test_pipeline_e2e.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/dependabot-maintenance-u1mdmh

---

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

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!