[Feature]: Make the PyPI project description render the CodeClone wordmark reliably #22

Feature category

Documentation

Why is this worth adding?

The current PyPI project page renders the top CodeClone wordmark incorrectly, which makes the release page look broken on the main package distribution surface.

GitHub README rendering is fine, but PyPI long descriptions have different constraints. A PyPI-friendly README path would improve first impression and packaging polish without changing any analysis behavior.

Problem statement

The README currently uses a theme-aware <picture> block with repo-relative SVG asset paths:

• docs/assets/codeclone-wordmark-dark.svg
• docs/assets/codeclone-wordmark.svg

This works on GitHub, but not on the PyPI project page. The wordmark area appears broken / missing, while badges and text render normally.

This appears to be caused by using repo-relative assets and GitHub-oriented HTML in a PyPI long-description context.

Proposed solution

Add a PyPI-friendly README path in the b6 line.

Preferred approach:

• keep the current GitHub-oriented README.md
• add README-pypi.md
• point [project].readme in pyproject.toml to the PyPI-friendly README for releases

In the PyPI README:

• replace the <picture> block with a single image
• use an absolute asset URL
• prefer PNG if it proves more reliable than SVG on PyPI

Alternatives considered

1. Keep one README and replace the top logo with a single absolute image URL for both GitHub and PyPI.
2. Use absolute URLs in the existing <picture> block.
3. Do nothing and accept the broken PyPI wordmark rendering.

Contract-sensitive areas

• Baseline / cache compatibility
• Canonical report JSON schema
• CLI exit codes or script-facing output
• MCP tool or resource semantics