Detect cross-project dependency conflicts in workspace reports

[codeforester]

Goal

Add workspace-level detection for obvious cross-project dependency and tool-version conflicts, starting with declared Base manifest data and project metadata that can be inspected safely.

Background

The v1.6.1 product evaluation identifies cross-project dependency conflict detection as a long-term workspace-intelligence play. Live Base already has workspace manifests, workspace status/check/doctor, project manifests, and read-only pyproject dependency metadata diagnostics, but it does not surface conflicts between sibling projects.

Scope

• Define the first conflict classes Base can detect without becoming a dependency solver.
• Start with declared Base artifacts, runtime/tool versions, Python manager/version constraints, and clearly comparable project metadata.
• Report conflicts at workspace scope through text and JSON output.
• Keep findings actionable, with links to the owning manifest/project and suggested next commands.
• Avoid resolving or installing dependency versions.
• Document unsupported cases such as transitive package resolution and lockfile solving.

Acceptance Criteria

• Workspace reports can identify at least one meaningful class of sibling-project conflict from deterministic local data.
• Findings include project names, conflicting declarations, source paths, severity, and suggested next actions.
• JSON output has stable keys and preserves existing workspace report compatibility.
• Base does not perform network dependency solving or mutate project files.
• Docs explain the boundary between conflict detection and package-manager ownership.

Validation

• Focused Python tests under base_projects for complete, conflicting, missing, and unsupported metadata cases.
• Docs updates for workspace report/check/doctor behavior.
• git diff --check.

Project Fields

• Priority: P2
• Status: Backlog
• Size: L
• Area: Workspace
• Initiative: Workspace Handling

Source

Derived from Base - Product Evaluation (v1.6.1).pdf, strategic action item 10.