feat: add deterministic boundary-quality eval for architecture plans (#316)

[azalio]

Summary

Implements #316 — adds a deterministic boundary_quality_report module that evaluates architectural decomposition plans for boundary quality. Works from blueprint.json data alone: no network, no model calls, no optional structural code-map (#310) required.

Changes

src/mapify_cli/boundary_quality_report.py (new module)

• is_architecture_heavy(blueprint) — detects refactor+large or 3+ arch-concern subtasks
• report_boundary_quality(blueprint) -> BoundaryQualityReport — runs all four advisory checks
• BoundaryQualityReport.as_dict() — JSON-serializable output

Four advisory checks (warn/info only — hard errors stay in validate_blueprint_contract):

• FILE_SHARED_ACROSS_BOUNDARIES (warn): same file in two unrelated subtasks — ownership ambiguous, concurrent writes will conflict
• CROSS_BOUNDARY_DEP_PRESSURE (warn): high-risk/large subtasks share a directory prefix but have no declared dependency
• REFACTOR_WITHOUT_TEST_PAIR (info): refactor subtask with no tests subtask that declares it as a dependency
• LOW_COHESION_SUBTASK (info): affected_files span 3+ top-level directories for non-permissive concern types (suppressed for refactor/docs/release/config)

Related subtasks (dependency edge in either direction) suppress FILE_SHARED and CROSS_BOUNDARY warnings.

tests/test_boundary_quality_report.py (new, 33 tests)

• VC1–VC3: architecture-heavy detection (True/False)
• VC4–VC5: FILE_SHARED_ACROSS_BOUNDARIES (fires + suppressed by dep)
• VC6–VC7: CROSS_BOUNDARY_DEP_PRESSURE (fires + suppressed by dep)
• VC8–VC9: REFACTOR_WITHOUT_TEST_PAIR (fires + suppressed by test dep)
• VC10–VC11: LOW_COHESION_SUBTASK (fires + suppressed for refactor/docs)
• VC12: clean blueprint → zero findings
• VC13: report contract (returns BoundaryQualityReport, summary dict, empty-blueprint safe)
• VC14: as_dict() JSON-serialisable

Acceptance criteria

• ✅ Deterministic helper produces boundary_quality_report for fixture blueprints without network or model calls
• ✅ Report distinguishes hard grounding errors (out of scope, handled by existing gates) from advisory quality warnings
• ✅ Tests include good split (zero findings) and bad split (shared file, cross-boundary pressure)
• ✅ Works without [CodeGraph] Add optional local structural code-map provider for MAP research #310 structural provider; integration with [CodeGraph] Add optional local structural code-map provider for MAP research #310 is a future enhancement
• ✅ No template sources touched, no render-templates needed

Test results

3342 passed, 4 skipped, 0 failures (full suite)
ruff: All checks passed
pyright: 0 errors, 0 warnings, 0 informations

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 21 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2669b601-9972-4ca4-ba96-8221fc6e9a2a

📥 Commits

Reviewing files that changed from the base of the PR and between a22f496 and ad4199a.

📒 Files selected for processing (2)

• src/mapify_cli/boundary_quality_report.py
• tests/test_boundary_quality_report.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/compassionate-cerf-5tugql

---

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.}