fix(open-core): scrub private repo names

[yakimoto]

Scrub private WAVE repo-name references from public files so the open-core content-policy guard passes.

Mapping applied:

• pyproject.toml [project.urls]: Repository and Issues wave-surfer-connect → this repo's own public URLs https://github.com/wave-av/sdk-python` (+ /issues)

Verified zero remaining hits via the guard grep (excluding public-repo-guard/** and .gitleaks.toml). No real package dependencies reference private packages.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation/metadata-only URL changes with no effect on package code, dependencies, or install behavior.

Overview
Updates pyproject.toml [project.urls] so Repository and Issues point at the public wave-av/sdk-python repo (and its issues page) instead of the private wave-surfer-connect names, so open-core content-policy checks pass.

No runtime or dependency behavior changes—metadata only.

^{Reviewed by Cursor Bugbot for commit 6cea898. Configure here.}

---

Summary by cubic

Replaced private repo URLs with public sdk-python links in pyproject.toml so the open-core content-policy guard passes. Updated [project.urls] Repository and Issues; no other private references remain.

^{Written for commit 6cea898. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6cea898

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

@yakimoto, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 11 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3bad4de2-4d9e-4336-8bc7-06f91373e349

📥 Commits

Reviewing files that changed from the base of the PR and between 3065203 and 6cea898.

📒 Files selected for processing (1)

• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/scrub-private-names-2026-06-09

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/scrub-private-names-2026-06-09

---

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

[wave-bugbot]

🟢 WAVE BugBot — clear

No confident findings on the changed lines.

_{Local review · $0 inference · wave-dispatch}