fix(packaging): point package readmes inside their project directories

[slin1237]

Description

Problem

Every e2e job dies in Install wheel and test dependencies since hatchling 1.27.0 released upstream (unpinned in pip's build env):

ValueError: Readme path must be within the project directory: ../../README.md

clients/python (hatchling backend, source-installed by ci_install_e2e_deps.sh in every e2e lane) and bindings/python (maturin, tolerant today but same latent defect) both declared readme = "../../README.md". First hit: #2087's run 31460158272 (20+ jobs down); main's post-#2060 run hits the same wall as its e2e installs proceed. Same failure class as #2086 — unpinned build tooling moved underneath us.

Solution

The metadata was always out-of-spec — a wheel embeds its readme, so a path outside the sdist boundary never round-tripped; older hatchling merely tolerated it. Point both packages at local readmes rather than pinning hatchling back: bindings/python already had a real README its pyproject was pointing past, and smg_client gets a short one describing the package.

Changes

• clients/python/README.md: new package readme; pyproject.toml points at it.
• bindings/python/pyproject.toml: point at the existing local README.md.

Test Plan

• Built the smg_client sdist against hatchling==1.27.0 exactly (the version that broke CI): succeeds; fails identically to CI before the fix.
• The e2e lanes on this PR exercise the real install path in every job.

Checklist

• cargo +nightly fmt passes (no Rust changes)
• cargo clippy --all-targets --all-features -- -D warnings passes (no Rust changes)
• (Optional) Documentation updated
• (Optional) Please join us on Slack #sig-smg to discuss, review, and merge PRs

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 24 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: a569ac96-067a-46f2-a6b5-803b6f675def

📥 Commits

Reviewing files that changed from the base of the PR and between d676365 and b124488.

📒 Files selected for processing (3)

• bindings/python/pyproject.toml
• clients/python/README.md
• clients/python/pyproject.toml

---

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

[claude]

Clean fix. Both pyproject.toml readme paths now correctly reference local files, resolving the hatchling 1.27.0 breakage. The new clients/python/README.md is accurate. No issues found.